syzbot


INFO: task hung in f2fs_balance_fs

Status: upstream: reported C repro on 2023/03/15 03:28
Subsystems: f2fs
[Documentation on labels]
Reported-by: syzbot+8b85865808c8908a0d8c@syzkaller.appspotmail.com
First crash: 574d, last: 6h18m
Cause bisection: introduced by (bisect log) :
commit 10d0786b39b3b91c4fbf8c2926e97ab456a4eea1
Author: Jia Yang <jiayang5@huawei.com>
Date: Wed Jul 14 07:46:06 2021 +0000

  f2fs: Revert "f2fs: Fix indefinite loop in f2fs_gc() v1"

Crash: INFO: task hung in f2fs_balance_fs (log)
Repro: C syz .config
  
Fix bisection: the issue occurs on the latest tested release (bisect log)
  
Discussions (8)
Title Replies (including bot) Last reply
[syzbot] Monthly f2fs report (Feb 2024) 0 (1) 2024/02/15 13:28
[syzbot] Monthly f2fs report (Nov 2023) 0 (1) 2023/11/22 09:42
[syzbot] Monthly f2fs report (Aug 2023) 0 (1) 2023/08/07 07:27
[syzbot] Monthly f2fs report (Jul 2023) 0 (1) 2023/07/07 08:54
[syzbot] Monthly f2fs report (Jun 2023) 0 (1) 2023/06/06 23:21
[syzbot] Monthly f2fs report (May 2023) 0 (1) 2023/05/05 21:40
[syzbot] Monthly f2fs report 0 (1) 2023/04/04 14:20
[syzbot] [f2fs?] INFO: task hung in f2fs_balance_fs 0 (3) 2023/03/26 16:58
Similar bugs (6)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-4.19 INFO: task hung in f2fs_balance_fs f2fs C 199 439d 579d 0/1 upstream: reported C repro on 2022/10/18 13:55
linux-6.1 INFO: task hung in f2fs_balance_fs (2) 2 173d 195d 0/3 auto-obsoleted due to no activity on 2024/03/06 18:04
linux-6.1 INFO: task hung in f2fs_balance_fs (3) origin:lts-only C done 37 7d15h 53d 0/3 upstream: reported C repro on 2024/03/27 06:53
linux-4.14 INFO: task hung in f2fs_balance_fs 3 548d 575d 0/1 auto-obsoleted due to no activity on 2023/03/18 03:56
linux-6.1 INFO: task hung in f2fs_balance_fs 20 375d 438d 0/3 auto-obsoleted due to no activity on 2023/08/22 15:19
linux-5.15 INFO: task hung in f2fs_balance_fs origin:upstream C 89 4d04h 438d 0/3 upstream: reported C repro on 2023/03/08 13:34
Last patch testing requests (9)
Created Duration User Patch Repo Result
2024/03/24 15:45 18m retest repro upstream error OK
2024/01/22 15:27 22m retest repro upstream OK log
2024/01/22 15:27 23m retest repro upstream OK log
2024/01/22 15:27 22m retest repro upstream OK log
2024/01/22 03:03 21m retest repro upstream OK log
2023/09/22 13:47 26m retest repro upstream report log
2023/09/22 13:47 33m retest repro upstream report log
2023/03/26 11:35 22m hdanton@sina.com patch https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 4bdec23f971b OK log
2023/03/26 07:22 16m hdanton@sina.com patch https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 4bdec23f971b report log

Sample crash report:
INFO: task kworker/u4:9:2429 blocked for more than 143 seconds.
      Not tainted 6.8.0-rc3-syzkaller-00215-ge6f39a90de92 #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/u4:9    state:D stack:20216 pid:2429  tgid:2429  ppid:2      flags:0x00004000
Workqueue: writeback wb_workfn (flush-7:0)
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5400 [inline]
 __schedule+0x177f/0x49a0 kernel/sched/core.c:6727
 __schedule_loop kernel/sched/core.c:6802 [inline]
 schedule+0x149/0x260 kernel/sched/core.c:6817
 schedule_preempt_disabled+0x13/0x30 kernel/sched/core.c:6874
 rwsem_down_write_slowpath+0xeea/0x13b0 kernel/locking/rwsem.c:1178
 __down_write_common+0x1ae/0x200 kernel/locking/rwsem.c:1306
 f2fs_down_write fs/f2fs/f2fs.h:2138 [inline]
 f2fs_balance_fs+0x500/0x730 fs/f2fs/segment.c:437
 f2fs_write_inode+0x3f0/0x470 fs/f2fs/inode.c:794
 write_inode fs/fs-writeback.c:1473 [inline]
 __writeback_single_inode+0x69f/0xfd0 fs/fs-writeback.c:1690
 writeback_sb_inodes+0x8e3/0x1220 fs/fs-writeback.c:1916
 __writeback_inodes_wb+0x11b/0x260 fs/fs-writeback.c:1987
 wb_writeback+0x461/0xc80 fs/fs-writeback.c:2094
 wb_check_background_flush fs/fs-writeback.c:2164 [inline]
 wb_do_writeback fs/fs-writeback.c:2252 [inline]
 wb_workfn+0xc33/0xfb0 fs/fs-writeback.c:2279
 process_one_work kernel/workqueue.c:2633 [inline]
 process_scheduled_works+0x913/0x1420 kernel/workqueue.c:2706
 worker_thread+0xa5f/0x1000 kernel/workqueue.c:2787
 kthread+0x2ef/0x390 kernel/kthread.c:388
 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147
 ret_from_fork_asm+0x1b/0x30 arch/x86/entry/entry_64.S:242
 </TASK>

Showing all locks held in the system:
1 lock held by khungtaskd/29:
 #0: ffffffff8e130ae0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:298 [inline]
 #0: ffffffff8e130ae0 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:750 [inline]
 #0: ffffffff8e130ae0 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x55/0x2a0 kernel/locking/lockdep.c:6614
4 locks held by kworker/u4:9/2429:
 #0: ffff888018ee1d38 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2608 [inline]
 #0: ffff888018ee1d38 ((wq_completion)writeback){+.+.}-{0:0}, at: process_scheduled_works+0x825/0x1420 kernel/workqueue.c:2706
 #1: ffffc90009ddfd20 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2608 [inline]
 #1: ffffc90009ddfd20 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_scheduled_works+0x825/0x1420 kernel/workqueue.c:2706
 #2: ffff88802c72c0e0 (&type->s_umount_key#43){.+.+}-{3:3}, at: super_trylock_shared+0x22/0xf0 fs/super.c:566
 #3: ffff888078bf92a8 (&sbi->gc_lock){+.+.}-{3:3}, at: f2fs_down_write fs/f2fs/f2fs.h:2138 [inline]
 #3: ffff888078bf92a8 (&sbi->gc_lock){+.+.}-{3:3}, at: f2fs_balance_fs+0x500/0x730 fs/f2fs/segment.c:437
1 lock held by syslogd/4493:
 #0: ffff8880b953c918 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested+0x2a/0x140 kernel/sched/core.c:559
2 locks held by getty/4809:
 #0: ffff88802ff920a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:243
 #1: ffffc90002f162f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6b4/0x1e10 drivers/tty/n_tty.c:2201
6 locks held by syz-executor242/5074:

=============================================

NMI backtrace for cpu 0
CPU: 0 PID: 29 Comm: khungtaskd Not tainted 6.8.0-rc3-syzkaller-00215-ge6f39a90de92 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x1e7/0x2e0 lib/dump_stack.c:106
 nmi_cpu_backtrace+0x49c/0x4d0 lib/nmi_backtrace.c:113
 nmi_trigger_cpumask_backtrace+0x198/0x320 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:160 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:222 [inline]
 watchdog+0xfaf/0xff0 kernel/hung_task.c:379
 kthread+0x2ef/0x390 kernel/kthread.c:388
 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147
 ret_from_fork_asm+0x1b/0x30 arch/x86/entry/entry_64.S:242
 </TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 22 Comm: ksoftirqd/1 Not tainted 6.8.0-rc3-syzkaller-00215-ge6f39a90de92 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024
RIP: 0010:free_unref_page_commit+0xc1/0x1140 mm/page_alloc.c:2440
Code: 04 21 84 c0 4c 89 44 24 40 0f 85 59 08 00 00 c7 84 24 a0 00 00 00 00 00 00 00 48 8d 5a 55 48 89 d8 48 c1 e8 03 42 0f b6 04 20 <84> c0 4c 89 6c 24 30 0f 85 64 08 00 00 d0 2b 41 83 f8 20 0f 83 3b
RSP: 0018:ffffc900001c78c0 EFLAGS: 00000a03
RAX: 0000000000000000 RBX: ffff8880b9542815 RCX: ffffc900001c7903
RDX: ffff8880b95427c0 RSI: ffff8880b95427c0 RDI: ffff88813fffa740
RBP: ffffc900001c79c8 R08: 0000000000000000 R09: 1ffffffff258a484
R10: dffffc0000000000 R11: fffffbfff258a485 R12: dffffc0000000000
R13: ffffea0001de7740 R14: 1ffff92000038f28 R15: 0000000000000000
FS:  0000000000000000(0000) GS:ffff8880b9500000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055ba051976d0 CR3: 000000001e5ba000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <NMI>
 </NMI>
 <TASK>
 free_unref_page+0x17c/0x3f0 mm/page_alloc.c:2509
 rcu_do_batch kernel/rcu/tree.c:2190 [inline]
 rcu_core+0xd76/0x1810 kernel/rcu/tree.c:2465
 __do_softirq+0x2bb/0x942 kernel/softirq.c:553
 run_ksoftirqd+0xc5/0x130 kernel/softirq.c:921
 smpboot_thread_fn+0x543/0xa30 kernel/smpboot.c:164
 kthread+0x2ef/0x390 kernel/kthread.c:388
 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147
 ret_from_fork_asm+0x1b/0x30 arch/x86/entry/entry_64.S:242
 </TASK>
INFO: NMI handler (nmi_cpu_backtrace_handler) took too long to run: 1.759 msecs

Crashes (449):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/02/10 05:12 upstream e6f39a90de92 77b23aa1 .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in f2fs_balance_fs
2023/11/16 23:52 upstream 7475e51b8796 cb976f63 .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in f2fs_balance_fs
2023/09/04 07:11 upstream db906f0ca6bb 696ea0d2 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-kasan-gce-smack-root INFO: task hung in f2fs_balance_fs
2023/06/09 08:31 upstream 25041a4c02c7 7086cdb9 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-kasan-gce-root INFO: task hung in f2fs_balance_fs
2023/03/26 05:17 upstream 4bdec23f971b fbf0499a .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-kasan-gce-root INFO: task hung in f2fs_balance_fs
2024/05/19 09:49 upstream 0450d2083be6 c0f1611a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in f2fs_balance_fs
2024/05/17 00:29 upstream 3c999d1ae3c7 c2e07261 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in f2fs_balance_fs
2024/05/16 21:14 upstream 3c999d1ae3c7 c2e07261 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in f2fs_balance_fs
2024/05/13 14:30 upstream a38297e3fb01 9026e142 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in f2fs_balance_fs
2024/05/12 20:58 upstream ba16c1cf11c9 9026e142 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in f2fs_balance_fs
2024/05/09 20:02 upstream 45db3ab70092 05079661 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in f2fs_balance_fs
2024/05/06 20:03 upstream dd5a440a31fa d884b519 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in f2fs_balance_fs
2024/05/05 19:22 upstream 7367539ad4b0 610f2a54 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in f2fs_balance_fs
2024/05/05 17:34 upstream 7367539ad4b0 610f2a54 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in f2fs_balance_fs
2024/05/05 16:04 upstream 7367539ad4b0 610f2a54 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in f2fs_balance_fs
2024/05/04 11:45 upstream ddb4c3f25b7b 610f2a54 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in f2fs_balance_fs
2024/05/03 08:08 upstream 49a73b1652c5 ddfc15a1 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in f2fs_balance_fs
2024/05/03 05:42 upstream 49a73b1652c5 ddfc15a1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in f2fs_balance_fs
2024/05/02 05:35 upstream 0106679839f7 3ba885bc .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in f2fs_balance_fs
2024/05/01 16:52 upstream 18daea77cca6 3ba885bc .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in f2fs_balance_fs
2024/05/01 13:22 upstream 18daea77cca6 3ba885bc .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in f2fs_balance_fs
2024/04/30 13:16 upstream 98369dccd2f8 3ce4924c .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in f2fs_balance_fs
2024/04/28 16:14 upstream 2c8159388952 07b455f9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in f2fs_balance_fs
2024/04/28 07:28 upstream 5d12ed4bea43 07b455f9 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in f2fs_balance_fs
2024/04/28 05:30 upstream 5d12ed4bea43 07b455f9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in f2fs_balance_fs
2024/04/28 01:22 upstream 5d12ed4bea43 07b455f9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in f2fs_balance_fs
2024/04/27 21:55 upstream 5d12ed4bea43 07b455f9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in f2fs_balance_fs
2024/04/27 20:14 upstream 5d12ed4bea43 07b455f9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in f2fs_balance_fs
2024/04/27 16:21 upstream 5eb4573ea63d 07b455f9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in f2fs_balance_fs
2024/04/27 12:37 upstream 5eb4573ea63d 07b455f9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in f2fs_balance_fs
2024/04/27 10:27 upstream 5eb4573ea63d 07b455f9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in f2fs_balance_fs
2024/04/27 06:15 upstream 5eb4573ea63d 07b455f9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in f2fs_balance_fs
2024/04/27 03:30 upstream 5eb4573ea63d 07b455f9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in f2fs_balance_fs
2024/04/27 02:12 upstream 5eb4573ea63d 059e9963 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in f2fs_balance_fs
2024/04/26 23:05 upstream c942a0cd3603 059e9963 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in f2fs_balance_fs
2024/04/26 21:44 upstream c942a0cd3603 059e9963 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in f2fs_balance_fs
2024/04/26 17:30 upstream c942a0cd3603 059e9963 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in f2fs_balance_fs
2024/04/25 22:37 upstream e33c4963bf53 8bdc0f22 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in f2fs_balance_fs
2024/04/25 15:29 upstream e88c4cfcb7b8 8bdc0f22 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in f2fs_balance_fs
2024/04/25 04:55 upstream e88c4cfcb7b8 8bdc0f22 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in f2fs_balance_fs
2024/04/23 05:02 upstream 4d2008430ce8 21339d7b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in f2fs_balance_fs
2024/04/22 06:51 upstream 48cf398f15fc af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in f2fs_balance_fs
2024/04/21 23:19 upstream 48cf398f15fc af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in f2fs_balance_fs
2024/04/21 09:54 upstream 977b1ef51866 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in f2fs_balance_fs
2024/03/10 14:41 upstream 005f6f34bd47 6ee49f2e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in f2fs_balance_fs
2024/03/10 07:14 upstream 09e5c48fea17 6ee49f2e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in f2fs_balance_fs
2024/03/10 03:55 upstream 09e5c48fea17 6ee49f2e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in f2fs_balance_fs
2024/03/10 00:16 upstream 09e5c48fea17 6ee49f2e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in f2fs_balance_fs
2024/03/09 17:32 upstream 10d48d70e82d 6ee49f2e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in f2fs_balance_fs
2024/03/09 06:12 upstream 10d48d70e82d 6ee49f2e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in f2fs_balance_fs
2024/03/09 02:05 upstream 10d48d70e82d 8e75c913 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in f2fs_balance_fs
2024/03/08 17:26 upstream 3aaa8ce7a335 8e75c913 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in f2fs_balance_fs
2024/03/06 10:44 upstream 29cd507cbec2 f39a7eed .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in f2fs_balance_fs
2023/03/04 22:39 upstream 0988a0ea7919 f8902b57 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in f2fs_balance_fs
2022/10/23 06:03 upstream 4da34b7d175d c0b80a55 .config console log report info [disk image] [vmlinux] ci2-upstream-fs INFO: task hung in f2fs_balance_fs
2024/05/05 14:17 linux-next 9221b2819b8a 610f2a54 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in f2fs_balance_fs
2024/05/04 14:22 linux-next 9221b2819b8a 610f2a54 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in f2fs_balance_fs
2024/04/29 01:29 linux-next bb7a2467e6be 07b455f9 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in f2fs_balance_fs
2024/04/22 17:50 linux-next 7b4f2bc91c15 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in f2fs_balance_fs
2024/04/22 17:22 linux-next 7b4f2bc91c15 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in f2fs_balance_fs
2024/02/28 09:46 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 9abbc24128bc d367cbe5 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 INFO: task hung in f2fs_balance_fs
* Struck through repros no longer work on HEAD.