All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] [Bug 216050] f2fs_gc occupies 100% cpu
Date: Tue, 11 Apr 2023 21:51:21 +0000	[thread overview]
Message-ID: <bug-216050-202145-s5GQiRS0Tg@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216050-202145@https.bugzilla.kernel.org/>

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

Ryotaro Ko (pikatenor@gmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |pikatenor@gmail.com

--- Comment #153 from Ryotaro Ko (pikatenor@gmail.com) ---
I applied the patch on the latest archlinux kernel (6.2.10-arch1
https://github.com/pikatenor/linux/tree/archlinux-6.2.10-f2fs) and tried it,
but f2fs_gc still hangs around 2 hours after boot.

[    0.000000] Linux version 6.2.10-arch1-1-test-507874-g453da3ddc42a
(linux-test@archlinux) (gcc (GCC) 12.2.1 20230201, GNU ld (GNU Binutils) 2.40)
#1 SMP PREEMPT_DYNAMIC Tue, 11 Apr 2023 16:26:44 +0000
[    0.000000] Command line: initrd=\initramfs-linux-test.img
cryptdevice=UUID=b5b188ee-8355-4638-b192-111ee6371c79:Homie
root=UUID=ca2eb962-9af0-4d5c-869d-9c1916f32a2e rw quiet i915.enable_psr=0

[ 9584.264309] INFO: task f2fs_ckpt-259:4:213 blocked for more than 122
seconds.
[ 9584.264313]       Tainted: G     U            
6.2.10-arch1-1-test-507874-g453da3ddc42a #1
[ 9584.264314] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
message.
[ 9584.264315] task:f2fs_ckpt-259:4 state:D stack:0     pid:213   ppid:2     
flags:0x00004000
[ 9584.264318] Call Trace:
[ 9584.264319]  <TASK>
[ 9584.264321]  __schedule+0x3c8/0x12e0
[ 9584.264326]  ? select_task_rq_fair+0x16c/0x1c00
[ 9584.264329]  ? update_load_avg+0x7e/0x780
[ 9584.264332]  schedule+0x5e/0xd0
[ 9584.264333]  rwsem_down_write_slowpath+0x329/0x700
[ 9584.264338]  ? __pfx_issue_checkpoint_thread+0x10/0x10 [f2fs
137a18329c9b4a66b7d5836126aee7155321bd82]
[ 9584.264366]  __checkpoint_and_complete_reqs+0x7a/0x1b0 [f2fs
137a18329c9b4a66b7d5836126aee7155321bd82]
[ 9584.264390]  ? __pfx_issue_checkpoint_thread+0x10/0x10 [f2fs
137a18329c9b4a66b7d5836126aee7155321bd82]
[ 9584.264411]  issue_checkpoint_thread+0x4c/0x110 [f2fs
137a18329c9b4a66b7d5836126aee7155321bd82]
[ 9584.264433]  ? __pfx_autoremove_wake_function+0x10/0x10
[ 9584.264437]  kthread+0xdb/0x110
[ 9584.264438]  ? __pfx_kthread+0x10/0x10
[ 9584.264440]  ret_from_fork+0x29/0x50
[ 9584.264445]  </TASK>
[ 9584.264508] INFO: task kworker/u16:2:19587 blocked for more than 122
seconds.
[ 9584.264509]       Tainted: G     U            
6.2.10-arch1-1-test-507874-g453da3ddc42a #1
[ 9584.264510] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
message.
[ 9584.264510] task:kworker/u16:2   state:D stack:0     pid:19587 ppid:2     
flags:0x00004000
[ 9584.264514] Workqueue: writeback wb_workfn (flush-259:0)
[ 9584.264517] Call Trace:
[ 9584.264518]  <TASK>
[ 9584.264519]  __schedule+0x3c8/0x12e0
[ 9584.264521]  ? ttwu_queue_wakelist+0xef/0x110
[ 9584.264524]  ? try_to_wake_up+0xd9/0x540
[ 9584.264527]  schedule+0x5e/0xd0
[ 9584.264528]  schedule_timeout+0x151/0x160
[ 9584.264531]  wait_for_completion+0x8a/0x160
[ 9584.264534]  f2fs_issue_checkpoint+0x11f/0x200 [f2fs
137a18329c9b4a66b7d5836126aee7155321bd82]
[ 9584.264558]  f2fs_balance_fs_bg+0x12e/0x390 [f2fs
137a18329c9b4a66b7d5836126aee7155321bd82]
[ 9584.264582]  f2fs_write_node_pages+0x78/0x240 [f2fs
137a18329c9b4a66b7d5836126aee7155321bd82]
[ 9584.264606]  do_writepages+0xc1/0x1d0
[ 9584.264610]  __writeback_single_inode+0x3d/0x360
[ 9584.264614]  writeback_sb_inodes+0x1ed/0x4a0
[ 9584.264618]  __writeback_inodes_wb+0x4c/0xf0
[ 9584.264621]  wb_writeback+0x204/0x2f0
[ 9584.264625]  wb_workfn+0x354/0x4f0
[ 9584.264627]  ? ttwu_queue_wakelist+0xef/0x110
[ 9584.264630]  process_one_work+0x1c5/0x3c0
[ 9584.264633]  worker_thread+0x51/0x390
[ 9584.264636]  ? __pfx_worker_thread+0x10/0x10
[ 9584.264638]  kthread+0xdb/0x110
[ 9584.264639]  ? __pfx_kthread+0x10/0x10
[ 9584.264641]  ret_from_fork+0x29/0x50
[ 9584.264645]  </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

  parent reply	other threads:[~2023-04-11 21:51 UTC|newest]

Thread overview: 182+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-30 11:28 [f2fs-dev] [Bug 216050] New: fsfs_gc occupies 100% cpu bugzilla-daemon
2022-05-30 11:52 ` [f2fs-dev] [Bug 216050] " bugzilla-daemon
2022-05-30 23:47 ` bugzilla-daemon
2022-05-31  0:51 ` bugzilla-daemon
2022-05-31 18:15 ` [f2fs-dev] [Bug 216050] f2fs_gc " bugzilla-daemon
2022-05-31 21:30 ` bugzilla-daemon
2022-06-01  2:24 ` bugzilla-daemon
2022-06-01  2:35 ` bugzilla-daemon
2022-06-01  2:35 ` bugzilla-daemon
2022-06-01  3:11 ` bugzilla-daemon
2022-06-01  3:19 ` bugzilla-daemon
2022-06-01  3:28 ` bugzilla-daemon
2022-06-01 11:27 ` bugzilla-daemon
2022-06-01 14:38 ` bugzilla-daemon
2022-06-01 15:19 ` bugzilla-daemon
2022-06-01 16:20 ` bugzilla-daemon
2022-06-01 18:22 ` bugzilla-daemon
2022-06-02  1:46 ` bugzilla-daemon
2022-06-02 15:13 ` bugzilla-daemon
2022-06-02 15:21 ` bugzilla-daemon
2022-06-02 21:50 ` bugzilla-daemon
2022-06-02 22:18 ` bugzilla-daemon
2022-06-03 20:49 ` bugzilla-daemon
2022-06-05 18:23 ` bugzilla-daemon
2022-06-13 19:20 ` bugzilla-daemon
2022-06-27 16:25 ` bugzilla-daemon
2022-06-29  9:07 ` bugzilla-daemon
2022-06-30 16:08 ` bugzilla-daemon
2022-06-30 16:11 ` bugzilla-daemon
2022-06-30 19:30 ` bugzilla-daemon
2022-06-30 19:35 ` bugzilla-daemon
2022-07-01  1:12 ` bugzilla-daemon
2022-07-01  1:21 ` bugzilla-daemon
2022-07-01  1:23 ` bugzilla-daemon
2022-07-01 21:15 ` bugzilla-daemon
2022-07-04  3:12 ` bugzilla-daemon
2022-07-20  0:10 ` bugzilla-daemon
2022-07-27 15:30 ` bugzilla-daemon
2022-07-27 15:33 ` bugzilla-daemon
2022-07-27 21:39 ` bugzilla-daemon
2022-07-27 21:43 ` bugzilla-daemon
2022-07-27 23:35 ` bugzilla-daemon
2022-07-28  7:23 ` bugzilla-daemon
2022-07-28  8:52 ` bugzilla-daemon
2022-07-28 22:30 ` bugzilla-daemon
2022-07-29  2:51 ` bugzilla-daemon
2022-08-02  7:53 ` bugzilla-daemon
2022-08-02  8:40 ` bugzilla-daemon
2022-08-02  8:51 ` bugzilla-daemon
2022-08-02 18:25 ` bugzilla-daemon
2022-08-03 19:55 ` bugzilla-daemon
2022-08-08 10:47 ` bugzilla-daemon
2022-08-09 19:17 ` bugzilla-daemon
2022-08-17  4:53 ` bugzilla-daemon
2022-08-17  5:08 ` bugzilla-daemon
2022-08-17 10:56 ` bugzilla-daemon
2022-08-21 15:55 ` bugzilla-daemon
2022-08-23 22:31 ` bugzilla-daemon
2022-08-23 22:40 ` bugzilla-daemon
2022-09-06 10:32 ` bugzilla-daemon
2022-09-20 19:55 ` bugzilla-daemon
2022-09-20 21:23 ` bugzilla-daemon
2022-09-23 18:45 ` bugzilla-daemon
2022-09-24 23:14 ` bugzilla-daemon
2022-10-21  2:47 ` bugzilla-daemon
2022-10-22  4:33 ` bugzilla-daemon
2022-10-23  6:11 ` bugzilla-daemon
2022-10-24 23:01 ` bugzilla-daemon
2022-10-27 22:58 ` bugzilla-daemon
2022-10-27 23:16 ` bugzilla-daemon
2022-10-27 23:26 ` bugzilla-daemon
2022-11-02 16:59 ` bugzilla-daemon
2022-11-03 15:43 ` bugzilla-daemon
2022-11-03 16:29 ` bugzilla-daemon
2022-11-03 16:44 ` bugzilla-daemon
2022-11-03 16:49 ` bugzilla-daemon
2022-11-03 16:52 ` bugzilla-daemon
2022-11-03 17:05 ` bugzilla-daemon
2022-11-07 18:41 ` bugzilla-daemon
2022-11-11  7:35 ` bugzilla-daemon
2022-11-11 11:12 ` bugzilla-daemon
2022-11-11 17:41 ` bugzilla-daemon
2022-11-11 17:44 ` bugzilla-daemon
2022-11-11 20:58 ` bugzilla-daemon
2022-11-11 20:59 ` bugzilla-daemon
2022-11-11 21:30 ` bugzilla-daemon
2022-11-14 21:04 ` bugzilla-daemon
2022-11-15  8:06 ` bugzilla-daemon
2022-11-15  8:08 ` bugzilla-daemon
2022-11-22  8:49 ` bugzilla-daemon
2022-11-22 21:53 ` bugzilla-daemon
2022-11-27  0:07 ` bugzilla-daemon
2022-11-27  0:15 ` bugzilla-daemon
2022-11-27  0:16 ` bugzilla-daemon
2022-12-01 22:38 ` bugzilla-daemon
2022-12-01 22:43 ` bugzilla-daemon
2022-12-01 23:00 ` bugzilla-daemon
2022-12-02  5:40 ` bugzilla-daemon
2022-12-02  6:24 ` bugzilla-daemon
2022-12-06 15:50 ` bugzilla-daemon
2022-12-06 15:53 ` bugzilla-daemon
2022-12-06 16:29 ` bugzilla-daemon
2022-12-06 18:37 ` bugzilla-daemon
2022-12-06 19:02 ` bugzilla-daemon
2022-12-06 19:10 ` bugzilla-daemon
2022-12-06 22:19 ` bugzilla-daemon
2022-12-06 22:57 ` bugzilla-daemon
2022-12-06 23:02 ` bugzilla-daemon
2022-12-07  0:00 ` bugzilla-daemon
2022-12-11 11:39 ` bugzilla-daemon
2022-12-12 20:38 ` bugzilla-daemon
2022-12-13 17:20 ` bugzilla-daemon
2022-12-13 19:01 ` bugzilla-daemon
2022-12-13 21:04 ` bugzilla-daemon
2022-12-13 22:49 ` bugzilla-daemon
2022-12-13 22:56 ` bugzilla-daemon
2022-12-13 22:59 ` bugzilla-daemon
2022-12-18 18:57 ` bugzilla-daemon
2022-12-21  0:47 ` bugzilla-daemon
2022-12-21  0:56 ` bugzilla-daemon
2022-12-21  0:58 ` bugzilla-daemon
2022-12-21  1:04 ` bugzilla-daemon
2022-12-21  2:45 ` bugzilla-daemon
2023-01-16 17:27 ` bugzilla-daemon
2023-01-19  9:51 ` bugzilla-daemon
2023-01-19 13:19 ` bugzilla-daemon
2023-01-19 13:42 ` bugzilla-daemon
2023-01-19 15:35 ` bugzilla-daemon
2023-01-19 15:42 ` bugzilla-daemon
2023-01-19 17:03 ` bugzilla-daemon
2023-01-19 18:41 ` bugzilla-daemon
2023-01-19 18:45 ` bugzilla-daemon
2023-02-21  9:29 ` bugzilla-daemon
2023-02-21  9:40 ` bugzilla-daemon
2023-02-21 10:58 ` bugzilla-daemon
2023-02-21 11:06 ` bugzilla-daemon
2023-02-21 11:27 ` bugzilla-daemon
2023-03-09 20:21 ` bugzilla-daemon
2023-03-10 10:03 ` bugzilla-daemon
2023-03-23 14:34 ` bugzilla-daemon
2023-03-23 21:39 ` bugzilla-daemon
2023-03-31 11:13 ` bugzilla-daemon
2023-04-05 20:45 ` bugzilla-daemon
2023-04-06 16:03 ` bugzilla-daemon
2023-04-06 16:34 ` bugzilla-daemon
2023-04-06 16:45 ` bugzilla-daemon
2023-04-06 16:55 ` bugzilla-daemon
2023-04-06 17:17 ` bugzilla-daemon
2023-04-06 17:54 ` bugzilla-daemon
2023-04-07 12:47 ` bugzilla-daemon
2023-04-07 15:12 ` bugzilla-daemon
2023-04-07 16:35 ` bugzilla-daemon
2023-04-07 17:08 ` bugzilla-daemon
2023-04-11 21:51 ` bugzilla-daemon [this message]
2023-04-12 17:49 ` bugzilla-daemon
2023-04-12 18:46 ` bugzilla-daemon
2023-04-12 19:49 ` bugzilla-daemon
2023-04-12 19:58 ` bugzilla-daemon
2023-04-13  0:56 ` bugzilla-daemon
2023-04-13  9:02 ` bugzilla-daemon
2023-05-05 16:10 ` bugzilla-daemon
2023-05-05 17:44 ` bugzilla-daemon
2023-05-05 17:54 ` bugzilla-daemon
2023-05-05 18:04 ` bugzilla-daemon
2023-05-05 18:53 ` bugzilla-daemon
2023-05-05 19:00 ` bugzilla-daemon
2023-05-05 22:38 ` bugzilla-daemon
2023-05-05 22:51 ` bugzilla-daemon
2023-05-05 23:17 ` bugzilla-daemon
2023-05-09 19:27 ` bugzilla-daemon
2023-05-10 13:12 ` bugzilla-daemon
2023-06-01 12:46 ` bugzilla-daemon
2023-06-08  7:21 ` bugzilla-daemon
2023-07-09 16:07 ` bugzilla-daemon
2023-07-10 17:15 ` bugzilla-daemon
2023-07-30 11:06 ` bugzilla-daemon
2023-08-03 10:13 ` bugzilla-daemon
2023-08-04  3:42 ` bugzilla-daemon
2023-08-05 19:38 ` bugzilla-daemon
2023-08-18 23:40 ` bugzilla-daemon
2023-08-20 10:18 ` bugzilla-daemon
2023-08-21  9:32 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-216050-202145-s5GQiRS0Tg@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.