On Thu, May 28, 2020 at 06:00:38AM +0000, bugzilla-daemon@xxxxxxxxxxxxxxxxxxx wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=207053 > > --- Comment #8 from Paul Furtado (paulfurtado91@xxxxxxxxx) --- > The patches that came from this issue have given us many weeks of stability now > and we were ready to declare this as totally fixed, however, we hit another > instance of this issue this week which I'm assuming is probably on a slightly > different and much rarer code path. > > Here's a link to the blocked tasks log (beware that it's 2MB due to endless > processes getting hung inside the container once the filesystem was frozen): > https://gist.githubusercontent.com/PaulFurtado/48253a6978763671f70dc94d933df851/raw/6bad12023ac56e9b6cb3dde771fcb5b15f0bd679/patched_kernel_fsfreeze_sys_w.log > This shows the eofblocks scan in the following (massaged) trace: [1259466.349224] Workqueue: xfs-eofblocks/nvme4n1 xfs_eofblocks_worker [xfs] [1259466.353550] Call Trace: [1259466.359370] schedule+0x2f/0xa0 [1259466.362297] rwsem_down_read_slowpath+0x196/0x530 [1259466.372467] __percpu_down_read+0x49/0x60 [1259466.375778] __sb_start_write+0x5b/0x60 [1259466.379139] xfs_trans_alloc+0x152/0x160 [xfs] [1259466.382715] xfs_free_eofblocks+0x12d/0x1f0 [xfs] [1259466.386407] xfs_inode_free_eofblocks+0x128/0x1a0 [xfs] [1259466.394058] xfs_inode_ag_walk.isra.17+0x1a7/0x410 [xfs] [1259466.536551] xfs_inode_ag_iterator_tag+0x73/0xb0 [xfs] [1259466.540235] xfs_eofblocks_worker+0x29/0x40 [xfs] [1259466.543748] process_one_work+0x195/0x380 [1259466.546996] worker_thread+0x30/0x390 [1259466.553449] kthread+0x113/0x130 [1259466.559579] ret_from_fork+0x1f/0x40 This should be addressed by upstream commit 4b674b9ac8529 ("xfs: acquire superblock freeze protection on eofblocks scans"), which causes xfs_eofblocks_worker() to bail unless it acquires freeze write protection. What exact kernel is this seen on? Brian > Thanks, > Paul > > -- > You are receiving this mail because: > You are watching the assignee of the bug. >
