From: bugzilla-daemon@kernel.org
To: linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] [Bug 216050] f2fs_gc occupies 100% cpu
Date: Tue, 23 Aug 2022 22:40:34 +0000 [thread overview]
Message-ID: <bug-216050-202145-cmm0Oimkq7@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216050-202145@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=216050
--- Comment #56 from bogdan.nicolae@gmail.com ---
Also, there is a another task hanging up with a call trace:
kernel: INFO: task mandb:13173 blocked for more than 122 seconds.
kernel: Not tainted 5.19.3-arch1-1 #1
kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
message.
kernel: task:mandb state:D stack: 0 pid:13173 ppid: 1
flags:0x00000002
kernel: Call Trace:
kernel: <TASK>
kernel: __schedule+0x356/0x11a0
kernel: ? ttwu_queue_wakelist+0xef/0x110
kernel: ? try_to_wake_up+0x23e/0x550
kernel: schedule+0x5e/0xd0
kernel: schedule_timeout+0x11c/0x150
kernel: __wait_for_common+0x94/0x1d0
kernel: ? usleep_range_state+0x90/0x90
kernel: f2fs_issue_checkpoint+0x11f/0x200 [f2fs
d8aa87b5c63297ab56225cbf829d392db2a7d54b]
kernel: ? f2fs_update_inode_page+0x3d/0x80 [f2fs
d8aa87b5c63297ab56225cbf829d392db2a7d54b]
kernel: f2fs_do_sync_file+0x18b/0x960 [f2fs
d8aa87b5c63297ab56225cbf829d392db2a7d54b]
kernel: __do_sys_msync+0x1d3/0x2c0
kernel: do_syscall_64+0x5f/0x90
kernel: ? syscall_exit_to_user_mode+0x1b/0x40
kernel: ? do_syscall_64+0x6b/0x90
kernel: ? exc_page_fault+0x74/0x170
kernel: entry_SYSCALL_64_after_hwframe+0x63/0xcd
kernel: RIP: 0033:0x7f48b6d377c4
kernel: RSP: 002b:00007ffeddb19528 EFLAGS: 00000202 ORIG_RAX: 000000000000001a
kernel: RAX: ffffffffffffffda RBX: 0000000000000f78 RCX: 00007f48b6d377c4
kernel: RDX: 0000000000000006 RSI: 0000000000004000 RDI: 00007f48b6e6a000
kernel: RBP: 000056363710af00 R08: 0000563636f48fc0 R09: 00000000035573fd
kernel: R10: 0000000000001000 R11: 0000000000000202 R12: 00000000000000a6
kernel: R13: 0000000000000000 R14: 0000563636f48fc0 R15: 000056363710af00
kernel: </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
next prev parent reply other threads:[~2022-08-23 22:40 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 [this message]
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
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-cmm0Oimkq7@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.