syzbot


INFO: task hung in f2fs_fallocate (5)

Status: auto-obsoleted due to no activity on 2025/08/28 03:32
Subsystems: f2fs
[Documentation on labels]
Reported-by: syzbot+d05837bec7673c4a18fe@syzkaller.appspotmail.com
First crash: 131d, last: 105d
Cause bisection: introduced by (bisect log) :
commit 00b35530811f2aa3d7ceec2dbada80861c7632a8
Author: Eric Dumazet <edumazet@google.com>
Date: Thu Feb 6 14:04:22 2025 +0000

  batman-adv: adopt netdev_hold() / netdev_put()

Crash: unregister_netdevice: waiting for DEV to become free (log)
Repro: C syz .config
  
Fix bisection: failed (error log, bisect log)
  
Discussions (2)
Title Replies (including bot) Last reply
[syzbot] Monthly f2fs report (Apr 2025) 0 (1) 2025/04/29 12:47
[syzbot] [f2fs?] INFO: task hung in f2fs_fallocate (5) 0 (1) 2025/04/24 17:15
Similar bugs (5)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream INFO: task hung in f2fs_fallocate (4) f2fs 1 11 243d 412d 0/29 auto-obsoleted due to no activity on 2025/03/28 19:38
upstream INFO: task hung in f2fs_fallocate (3) f2fs 1 3 538d 554d 0/29 auto-obsoleted due to no activity on 2024/06/07 18:19
upstream INFO: task hung in f2fs_fallocate f2fs 1 1 869d 869d 0/29 auto-obsoleted due to no activity on 2023/07/12 13:35
upstream INFO: task hung in f2fs_fallocate (2) f2fs 1 3 651d 653d 0/29 auto-obsoleted due to no activity on 2024/02/15 04:04
linux-5.15 INFO: task hung in f2fs_fallocate 1 2 313d 313d 0/3 auto-obsoleted due to no activity on 2025/01/28 07:01
Last patch testing requests (2)
Created Duration User Patch Repo Result
2025/08/28 03:09 21m retest repro upstream OK log
2025/05/15 23:49 17m retest repro upstream report log

Sample crash report:
INFO: task syz.4.169:7619 blocked for more than 143 seconds.
      Not tainted 6.15.0-rc4-syzkaller-00051-g7a13c14ee59d #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.4.169       state:D stack:28360 pid:7619  tgid:7578  ppid:6925   task_flags:0x400040 flags:0x00000004
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5382 [inline]
 __schedule+0x168f/0x4c70 kernel/sched/core.c:6767
 __schedule_loop kernel/sched/core.c:6845 [inline]
 schedule+0x165/0x360 kernel/sched/core.c:6860
 schedule_preempt_disabled+0x13/0x30 kernel/sched/core.c:6917
 rwsem_down_write_slowpath+0xbec/0x1030 kernel/locking/rwsem.c:1176
 __down_write_common kernel/locking/rwsem.c:1304 [inline]
 __down_write kernel/locking/rwsem.c:1313 [inline]
 down_write+0x1ab/0x1f0 kernel/locking/rwsem.c:1578
 inode_lock include/linux/fs.h:867 [inline]
 f2fs_fallocate+0x24e/0x990 fs/f2fs/file.c:1940
 vfs_fallocate+0x6a0/0x830 fs/open.c:338
 ioctl_preallocate fs/ioctl.c:290 [inline]
 file_ioctl fs/ioctl.c:-1 [inline]
 do_vfs_ioctl+0x1b8f/0x1eb0 fs/ioctl.c:885
 __do_sys_ioctl fs/ioctl.c:904 [inline]
 __se_sys_ioctl+0x82/0x170 fs/ioctl.c:892
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xf6/0x210 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f9c44f8e969
RSP: 002b:00007f9c45e35038 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f9c451b6160 RCX: 00007f9c44f8e969
RDX: 0000200000000000 RSI: 0000000040305828 RDI: 0000000000000004
RBP: 00007f9c45010ab1 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000001 R14: 00007f9c451b6160 R15: 00007ffc9b06cc48
 </TASK>

Showing all locks held in the system:
1 lock held by kthreadd/2:
 #0: ffff8880b89399d8 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested+0x2a/0x140 kernel/sched/core.c:605
1 lock held by khungtaskd/31:
 #0: ffffffff8df3b860 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:331 [inline]
 #0: ffffffff8df3b860 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:841 [inline]
 #0: ffffffff8df3b860 (rcu_read_lock){....}-{1:3}, at: debug_show_all_locks+0x2e/0x180 kernel/locking/lockdep.c:6764
2 locks held by getty/5575:
 #0: ffff8880352120a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:243
 #1: ffffc900033332f0 (&ldata->atomic_read_lock){+.+.}-{4:4}, at: n_tty_read+0x43e/0x1400 drivers/tty/n_tty.c:2222
1 lock held by udevd/5973:
4 locks held by syz.4.169/7579:
2 locks held by syz.4.169/7619:
 #0: ffff888059002420 (sb_writers#15){.+.+}-{0:0}, at: file_start_write include/linux/fs.h:3041 [inline]
 #0: ffff888059002420 (sb_writers#15){.+.+}-{0:0}, at: vfs_fallocate+0x62a/0x830 fs/open.c:337
 #1: ffff888078af0a38 (&sb->s_type->i_mutex_key#23){++++}-{4:4}, at: inode_lock include/linux/fs.h:867 [inline]
 #1: ffff888078af0a38 (&sb->s_type->i_mutex_key#23){++++}-{4:4}, at: f2fs_fallocate+0x24e/0x990 fs/f2fs/file.c:1940
2 locks held by syz.9.354/9924:
 #0: ffffffff8e66a228 (bio_slab_lock){+.+.}-{4:4}, at: bio_put_slab block/bio.c:140 [inline]
 #0: ffffffff8e66a228 (bio_slab_lock){+.+.}-{4:4}, at: bioset_exit+0x44a/0x690 block/bio.c:1664
 #1: ffffffff8df41200 (rcu_state.barrier_mutex){+.+.}-{4:4}, at: rcu_barrier+0x4c/0x570 kernel/rcu/tree.c:3774
4 locks held by syz.1.359/10023:
3 locks held by sed/10050:

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

NMI backtrace for cpu 0
CPU: 0 UID: 0 PID: 31 Comm: khungtaskd Not tainted 6.15.0-rc4-syzkaller-00051-g7a13c14ee59d #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/19/2025
Call Trace:
 <TASK>
 dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120
 nmi_cpu_backtrace+0x39e/0x3d0 lib/nmi_backtrace.c:113
 nmi_trigger_cpumask_backtrace+0x17a/0x300 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:158 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:274 [inline]
 watchdog+0xfee/0x1030 kernel/hung_task.c:437
 kthread+0x70e/0x8a0 kernel/kthread.c:464
 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:153
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
 </TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 UID: 0 PID: 7579 Comm: syz.4.169 Not tainted 6.15.0-rc4-syzkaller-00051-g7a13c14ee59d #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/19/2025
RIP: 0010:check_preemption_disabled+0x1/0x120 lib/smp_processor_id.c:13
Code: 00 fa c0 8b 48 c7 c6 40 fa c0 8b eb 1c 66 66 66 2e 0f 1f 84 00 00 00 00 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 55 <41> 57 41 56 53 48 83 ec 10 65 48 8b 05 4e 1e 23 07 48 89 44 24 08
RSP: 0018:ffffc9000afe74a8 EFLAGS: 00000046
RAX: 0000000000000003 RBX: 0000000000000000 RCX: 6a5aeafeefa16e00
RDX: 0000000000000000 RSI: ffffffff8d9208e6 RDI: ffffffff8bc0fa60
RBP: 00000000ffffffff R08: ffff888030b83c00 R09: 0000000000000002
R10: 00000000ffffffc3 R11: 0000000000000002 R12: 0000000000000246
R13: ffff888030b83c00 R14: ffffffff8df3b920 R15: 0000000000000003
FS:  00007f9c45e776c0(0000) GS:ffff888126200000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00005623bb878950 CR3: 0000000032ea6000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 lockdep_recursion_finish kernel/locking/lockdep.c:472 [inline]
 lock_is_held_type+0xfe/0x190 kernel/locking/lockdep.c:5939
 lock_is_held include/linux/lockdep.h:249 [inline]
 __might_resched+0xf5/0x610 kernel/sched/core.c:8780
 down_read+0x22/0x2e0 kernel/locking/rwsem.c:1523
 f2fs_down_read fs/f2fs/f2fs.h:2197 [inline]
 f2fs_lock_op fs/f2fs/f2fs.h:2276 [inline]
 f2fs_allocate_pinning_section+0x3a/0x5d0 fs/f2fs/segment.c:3308
 f2fs_expand_inode_data+0x61d/0xaf0 fs/f2fs/file.c:1865
 f2fs_fallocate+0x4f5/0x990 fs/f2fs/file.c:1975
 vfs_fallocate+0x6a0/0x830 fs/open.c:338
 ioctl_preallocate fs/ioctl.c:290 [inline]
 file_ioctl fs/ioctl.c:-1 [inline]
 do_vfs_ioctl+0x1b8f/0x1eb0 fs/ioctl.c:885
 __do_sys_ioctl fs/ioctl.c:904 [inline]
 __se_sys_ioctl+0x82/0x170 fs/ioctl.c:892
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xf6/0x210 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f9c44f8e969
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f9c45e77038 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f9c451b5fa0 RCX: 00007f9c44f8e969
RDX: 00002000000000c0 RSI: 0000000040305828 RDI: 0000000000000004
RBP: 00007f9c45010ab1 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007f9c451b5fa0 R15: 00007ffc9b06cc48
 </TASK>

Crashes (3):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/04/30 23:20 upstream 7a13c14ee59d ce7952f4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in f2fs_fallocate
2025/04/20 16:55 upstream 119009db2674 2a20f901 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs INFO: task hung in f2fs_fallocate
2025/04/20 14:12 upstream 119009db2674 2a20f901 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in f2fs_fallocate
* Struck through repros no longer work on HEAD.