[f2fs-dev] [Bug 216050] f2fs_gc occupies 100% cpu

[bugzilla-daemon@kernel.org]

https://bugzilla.kernel.org/show_bug.cgi?id=216050

Sebastian Goth (linux@sgoth.de) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |linux@sgoth.de

--- Comment #57 from Sebastian Goth (linux@sgoth.de) ---
I started to see this on 5.19.6-arch1-1 out of the blue. Noticed the first time
while processing pacman post-install hooks hanging, so actually working on the
FS.
Now the system was essentially idle when f2fs_gc grabbed a core again. 


INFO: task f2fs_ckpt-259:2:377 blocked for more than 122 seconds.
      Tainted: P           OE     5.19.6-arch1-1 #1
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:f2fs_ckpt-259:2 state:D stack:    0 pid:  377 ppid:     2 flags:0x00004000
Call Trace:
 <TASK>
 __schedule+0x356/0x11a0
 ? preempt_schedule+0x43/0x60
 schedule+0x5e/0xd0
 rwsem_down_write_slowpath+0x335/0x720
 ? __schedule+0x35e/0x11a0
 ? __checkpoint_and_complete_reqs+0x1b0/0x1b0 [f2fs
9fac87d5629570e172d2b77a90a74b98e0678f12]
 __checkpoint_and_complete_reqs+0x7a/0x1b0 [f2fs
9fac87d5629570e172d2b77a90a74b98e0678f12]
 ? __checkpoint_and_complete_reqs+0x1b0/0x1b0 [f2fs
9fac87d5629570e172d2b77a90a74b98e0678f12]
 issue_checkpoint_thread+0x4c/0x110 [f2fs
9fac87d5629570e172d2b77a90a74b98e0678f12]
 ? cpuacct_percpu_seq_show+0x20/0x20
 kthread+0xdb/0x110
 ? kthread_complete_and_exit+0x20/0x20
 ret_from_fork+0x1f/0x30
 </TASK>
INFO: task kworker/u64:0:5076 blocked for more than 122 seconds.
      Tainted: P           OE     5.19.6-arch1-1 #1
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/u64:0   state:D stack:    0 pid: 5076 ppid:     2 flags:0x00004000
Workqueue: writeback wb_workfn (flush-259:0)
Call Trace:
 <TASK>
 __schedule+0x356/0x11a0
 ? ttwu_queue_wakelist+0xef/0x110
 schedule+0x5e/0xd0
 schedule_timeout+0x11c/0x150
 __wait_for_common+0x91/0x1d0
 ? usleep_range_state+0x90/0x90
 f2fs_issue_checkpoint+0x11f/0x200 [f2fs
9fac87d5629570e172d2b77a90a74b98e0678f12]
 f2fs_balance_fs_bg+0x119/0x370 [f2fs 9fac87d5629570e172d2b77a90a74b98e0678f12]
 f2fs_write_node_pages+0x78/0x240 [f2fs
9fac87d5629570e172d2b77a90a74b98e0678f12]
 do_writepages+0xc1/0x1d0
 ? __percpu_counter_sum+0x5b/0x70
 ? sched_clock_cpu+0xd/0xb0
 __writeback_single_inode+0x3d/0x360
 writeback_sb_inodes+0x1ed/0x4a0
 ? pollwake+0x78/0xa0
 __writeback_inodes_wb+0x4c/0xf0
 wb_writeback+0x204/0x2f0
 wb_workfn+0x36f/0x520
 process_one_work+0x1c4/0x380
 worker_thread+0x51/0x390
 ? rescuer_thread+0x3b0/0x3b0
 kthread+0xdb/0x110
 ? kthread_complete_and_exit+0x20/0x20
 ret_from_fork+0x1f/0x30
 </TASK>

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel