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: 773d, last: 3d11h
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 (12)
Title Replies (including bot) Last reply
[syzbot] Monthly f2fs report (Nov 2024) 0 (1) 2024/11/18 12:39
[syzbot] Monthly f2fs report (Oct 2024) 0 (1) 2024/10/18 07:31
[syzbot] Monthly f2fs report (Sep 2024) 0 (1) 2024/09/16 12:35
[syzbot] Monthly f2fs report (Aug 2024) 0 (1) 2024/08/16 19:58
[syzbot] [f2fs?] INFO: task hung in f2fs_balance_fs 1 (5) 2024/06/04 15:40
[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
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 638d 778d 0/1 upstream: reported C repro on 2022/10/18 13:55
linux-6.1 INFO: task hung in f2fs_balance_fs (2) 2 372d 394d 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 165 41d 252d 0/3 upstream: reported C repro on 2024/03/27 06:53
linux-4.14 INFO: task hung in f2fs_balance_fs 3 747d 774d 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 574d 637d 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 477 13h11m 637d 0/3 upstream: reported C repro on 2023/03/08 13:34
Last patch testing requests (10)
Created Duration User Patch Repo Result
2024/06/04 15:12 19m chao@kernel.org https://git.kernel.org/pub/scm/linux/kernel/git/chao/linux.git wip OK log
2024/03/24 15:45 18m retest repro upstream error
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/u8:1:12 blocked for more than 143 seconds.
      Not tainted 6.12.0-rc6-syzkaller-00169-g906bd684e4b1 #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/u8:1    state:D stack:24080 pid:12    tgid:12    ppid:2      flags:0x00004000
Workqueue: writeback wb_workfn (flush-7:0)
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5328 [inline]
 __schedule+0x17fa/0x4bd0 kernel/sched/core.c:6690
 __schedule_loop kernel/sched/core.c:6767 [inline]
 schedule+0x14b/0x320 kernel/sched/core.c:6782
 schedule_preempt_disabled+0x13/0x30 kernel/sched/core.c:6839
 rwsem_down_write_slowpath+0xeee/0x13b0 kernel/locking/rwsem.c:1176
 __down_write_common kernel/locking/rwsem.c:1304 [inline]
 __down_write kernel/locking/rwsem.c:1313 [inline]
 down_write+0x1d7/0x220 kernel/locking/rwsem.c:1578
 f2fs_down_write fs/f2fs/f2fs.h:2199 [inline]
 f2fs_balance_fs+0x5b0/0x7a0 fs/f2fs/segment.c:448
 f2fs_write_inode+0x3a0/0x4d0 fs/f2fs/inode.c:787
 write_inode fs/fs-writeback.c:1503 [inline]
 __writeback_single_inode+0x711/0x10d0 fs/fs-writeback.c:1723
 writeback_sb_inodes+0x80c/0x1370 fs/fs-writeback.c:1954
 __writeback_inodes_wb+0x11b/0x260 fs/fs-writeback.c:2025
 wb_writeback+0x42f/0xbd0 fs/fs-writeback.c:2136
 wb_check_background_flush fs/fs-writeback.c:2206 [inline]
 wb_do_writeback fs/fs-writeback.c:2294 [inline]
 wb_workfn+0xc58/0x1090 fs/fs-writeback.c:2321
 process_one_work kernel/workqueue.c:3229 [inline]
 process_scheduled_works+0xa63/0x1850 kernel/workqueue.c:3310
 worker_thread+0x870/0xd30 kernel/workqueue.c:3391
 kthread+0x2f0/0x390 kernel/kthread.c:389
 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
 </TASK>

Showing all locks held in the system:
4 locks held by kworker/u8:1/12:
 #0: ffff8881422b9148 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3204 [inline]
 #0: ffff8881422b9148 ((wq_completion)writeback){+.+.}-{0:0}, at: process_scheduled_works+0x93b/0x1850 kernel/workqueue.c:3310
 #1: ffffc90000117d00 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3205 [inline]
 #1: ffffc90000117d00 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_scheduled_works+0x976/0x1850 kernel/workqueue.c:3310
 #2: ffff88807e3060e0 (&type->s_umount_key#44){.+.+}-{3:3}, at: super_trylock_shared+0x22/0xf0 fs/super.c:562
 #3: ffff888012ff1350 (&sbi->gc_lock){+.+.}-{3:3}, at: f2fs_down_write fs/f2fs/f2fs.h:2199 [inline]
 #3: ffff888012ff1350 (&sbi->gc_lock){+.+.}-{3:3}, at: f2fs_balance_fs+0x5b0/0x7a0 fs/f2fs/segment.c:448
1 lock held by ksoftirqd/0/16:
1 lock held by khungtaskd/30:
 #0: ffffffff8e937da0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:337 [inline]
 #0: ffffffff8e937da0 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:849 [inline]
 #0: ffffffff8e937da0 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x55/0x2a0 kernel/locking/lockdep.c:6720
2 locks held by getty/5595:
 #0: ffff888031bb90a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:243
 #1: ffffc90002f062f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6a6/0x1e00 drivers/tty/n_tty.c:2211
5 locks held by syz-executor514/5850:

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

NMI backtrace for cpu 1
CPU: 1 UID: 0 PID: 30 Comm: khungtaskd Not tainted 6.12.0-rc6-syzkaller-00169-g906bd684e4b1 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/30/2024
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:94 [inline]
 dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120
 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:162 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:223 [inline]
 watchdog+0xff4/0x1040 kernel/hung_task.c:379
 kthread+0x2f0/0x390 kernel/kthread.c:389
 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
 </TASK>
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 UID: 0 PID: 5850 Comm: syz-executor514 Not tainted 6.12.0-rc6-syzkaller-00169-g906bd684e4b1 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/30/2024
RIP: 0010:__kasan_check_write+0x4/0x20 mm/kasan/shadow.c:37
Code: 31 d2 e9 6f e6 ff ff 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 f3 0f 1e fa <89> f6 48 8b 0c 24 ba 01 00 00 00 e9 3c e6 ff ff 66 2e 0f 1f 84 00
RSP: 0018:ffffc90003fa6b40 EFLAGS: 00000202
RAX: 0000000000000000 RBX: 0000000000000002 RCX: ffffffff81ccf56e
RDX: ffff88807e07bc00 RSI: 0000000000000004 RDI: ffffea0001e089b4
RBP: 1ffffd40003c1136 R08: ffffffff81ccf58f R09: 1ffffd40003c1136
R10: dffffc0000000000 R11: fffff940003c1137 R12: dffffc0000000000
R13: dffffc0000000000 R14: ffffffff81ccf4ae R15: ffffea0001e089b4
FS:  0000555568fb4380(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000556439a1f600 CR3: 000000007aa5a000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <NMI>
 </NMI>
 <TASK>
 instrument_atomic_read_write include/linux/instrumented.h:96 [inline]
 atomic_add_unless include/linux/atomic/atomic-instrumented.h:1517 [inline]
 page_ref_add_unless include/linux/page_ref.h:238 [inline]
 folio_ref_add_unless include/linux/page_ref.h:248 [inline]
 folio_try_get+0x114/0x350 include/linux/page_ref.h:264
 filemap_get_entry+0x240/0x3b0 mm/filemap.c:1852
 __filemap_get_folio+0x71/0xbd0 mm/filemap.c:1887
 pagecache_get_page+0x2c/0x200 mm/folio-compat.c:81
 find_get_page_flags include/linux/pagemap.h:830 [inline]
 f2fs_grab_cache_page+0x2b/0x320 fs/f2fs/f2fs.h:2784
 __get_node_page+0x131/0xfc0 fs/f2fs/node.c:1449
 is_alive fs/f2fs/gc.c:1149 [inline]
 gc_data_segment fs/f2fs/gc.c:1581 [inline]
 do_garbage_collect+0x259d/0x8210 fs/f2fs/gc.c:1829
 f2fs_gc+0xf90/0x2ff0 fs/f2fs/gc.c:1933
 f2fs_balance_fs+0x5f8/0x7a0 fs/f2fs/segment.c:450
 f2fs_map_blocks+0x44ec/0x4f10 fs/f2fs/data.c:1788
 f2fs_expand_inode_data+0x622/0xbb0 fs/f2fs/file.c:1811
 f2fs_fallocate+0x448/0x960 fs/f2fs/file.c:1914
 vfs_fallocate+0x569/0x6e0 fs/open.c:333
 ksys_fallocate fs/open.c:356 [inline]
 __do_sys_fallocate fs/open.c:364 [inline]
 __se_sys_fallocate fs/open.c:362 [inline]
 __x64_sys_fallocate+0xbd/0x110 fs/open.c:362
 do_syscall_x64 arch/x86/entry/common.c:52 [inline]
 do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fd1f9525dd9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 17 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffcad636958 EFLAGS: 00000246 ORIG_RAX: 000000000000011d
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fd1f9525dd9
RDX: 0000000000000009 RSI: 0000000000000000 RDI: 0000000000000004
RBP: 00007fd1f959f5f0 R08: 0000555568fb54c0 R09: 0000555568fb54c0
R10: 0000000000000022 R11: 0000000000000246 R12: 00007ffcad636980
R13: 00007ffcad636ba8 R14: 431bde82d7b634db R15: 00007fd1f956f03b
 </TASK>
INFO: NMI handler (nmi_cpu_backtrace_handler) took too long to run: 1.797 msecs

Crashes (1192):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/11/08 07:23 upstream 906bd684e4b1 179b040e .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in f2fs_balance_fs
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
2024/11/13 21:50 upstream f1b785f4c787 4dfba277 .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro] ci-snapshot-upstream-root INFO: task hung in f2fs_balance_fs
2024/11/29 03:51 upstream 7af08b57bcb9 5df23865 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in f2fs_balance_fs
2024/11/19 23:45 upstream 158f238aa69d 7d02db5a .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in f2fs_balance_fs
2024/10/26 23:40 upstream 850925a8133c 65e8686b .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro #1] [mounted in repro #2] ci-upstream-kasan-gce-root INFO: task hung in f2fs_balance_fs
2024/10/13 11:15 upstream 7234e2ea0edd 084d8178 .config console log report syz / log [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/11/29 19:24 upstream 7af08b57bcb9 5df23865 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in f2fs_balance_fs
2024/11/26 07:56 upstream 9f16d5e6f220 11dbc254 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in f2fs_balance_fs
2024/11/25 22:21 upstream 9f16d5e6f220 11dbc254 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in f2fs_balance_fs
2024/11/20 18:00 upstream bf9aa14fc523 4fca1650 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in f2fs_balance_fs
2024/11/20 09:00 upstream bf9aa14fc523 7d02db5a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in f2fs_balance_fs
2024/11/19 01:43 upstream 23acd177540d 571351cb .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in f2fs_balance_fs
2024/11/17 16:42 upstream 4a5df3796467 cfe3a04a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in f2fs_balance_fs
2024/11/17 05:38 upstream b5a24181e461 cfe3a04a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in f2fs_balance_fs
2024/11/14 11:31 upstream 0a9b9d17f3a7 a8c99394 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in f2fs_balance_fs
2024/11/13 19:04 upstream f1b785f4c787 a8c99394 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in f2fs_balance_fs
2024/11/11 22:07 upstream 2d5404caa8c7 0c4b1325 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in f2fs_balance_fs
2024/11/10 23:41 upstream a9cda7c0ffed 6b856513 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in f2fs_balance_fs
2024/11/09 19:42 upstream da4373fbcf00 6b856513 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in f2fs_balance_fs
2024/11/05 16:14 upstream 2e1b3cc9d7f7 da38b4c9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in f2fs_balance_fs
2024/11/03 10:38 upstream 3e5e6c9900c3 f00eed24 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in f2fs_balance_fs
2024/10/27 12:46 upstream 850925a8133c 65e8686b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in f2fs_balance_fs
2024/10/25 02:25 upstream 4e46774408d9 c79b8ca5 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in f2fs_balance_fs
2024/10/24 20:04 upstream c2ee9f594da8 0d144d1a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in f2fs_balance_fs
2024/10/24 19:12 upstream c2ee9f594da8 9fc8fe02 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in f2fs_balance_fs
2024/10/24 13:15 upstream c2ee9f594da8 0d144d1a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in f2fs_balance_fs
2024/10/23 23:26 upstream c2ee9f594da8 15fa2979 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in f2fs_balance_fs
2024/10/23 22:19 upstream c2ee9f594da8 15fa2979 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in f2fs_balance_fs
2024/10/23 17:36 upstream c2ee9f594da8 15fa2979 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in f2fs_balance_fs
2024/10/23 09:06 upstream c2ee9f594da8 15fa2979 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in f2fs_balance_fs
2024/10/23 07:05 upstream c2ee9f594da8 15fa2979 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in f2fs_balance_fs
2024/10/23 00:03 upstream c2ee9f594da8 15fa2979 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in f2fs_balance_fs
2024/10/22 22:46 upstream c2ee9f594da8 9d74f456 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in f2fs_balance_fs
2024/10/22 22:34 upstream c2ee9f594da8 9d74f456 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in f2fs_balance_fs
2024/10/22 21:30 upstream c2ee9f594da8 a93682b3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in f2fs_balance_fs
2024/10/22 17:58 upstream c2ee9f594da8 a93682b3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in f2fs_balance_fs
2024/10/22 11:33 upstream c2ee9f594da8 a93682b3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in f2fs_balance_fs
2024/06/23 06:31 upstream 5f583a3162ff edc5149a .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/24 19:51 upstream 8f6a15f095a6 8f98448e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root 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/12/01 05:28 linux-next f486c8aa16b8 68914665 .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/11/25 00:19 linux-next cfba9f07a1d6 68da6d95 .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/11/10 11:47 linux-next 929beafbe7ac 6b856513 .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/11/04 08:38 linux-next 1ffec08567f4 f00eed24 .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/11/03 03:27 linux-next c88416ba074a f00eed24 .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/11/01 11:02 linux-next c88416ba074a 96eb609f .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/10/30 12:44 linux-next 86e3904dcdc7 66aeb999 .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/11/12 08:34 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 563047e691f2 75bb1b32 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 INFO: task hung in f2fs_balance_fs
2024/10/24 02:59 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci ce8e69898653 15fa2979 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 INFO: task hung in f2fs_balance_fs
2024/10/23 13:28 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci df1aa7b14127 15fa2979 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 INFO: task hung in f2fs_balance_fs
2024/10/23 04:52 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 526116b79e8c 15fa2979 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 INFO: task hung in f2fs_balance_fs
2024/10/22 16:44 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 526116b79e8c 9d74f456 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 INFO: task hung in f2fs_balance_fs
2024/10/22 08:02 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 86cada34bc3a a93682b3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 INFO: task hung in f2fs_balance_fs
2024/10/22 07:51 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 86cada34bc3a a93682b3 .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.