syzbot


INFO: task hung in fdget_pos

Status: upstream: reported C repro on 2024/10/09 10:20
Subsystems: bcachefs
[Documentation on labels]
Reported-by: syzbot+0ee1ef35cf7e70ce55d7@syzkaller.appspotmail.com
First crash: 281d, last: 1d22h
Cause bisection: the issue happens on the oldest tested release (bisect log)
Crash: BUG: sleeping function called from invalid context in __getblk_gfp (log)
Repro: syz .config
  
Fix bisection: the issue occurs on the latest tested release (bisect log)
  
Discussions (4)
Title Replies (including bot) Last reply
[syzbot] Monthly kernfs report (Feb 2025) 0 (1) 2025/02/16 21:54
[syzbot] Monthly kernfs report (Nov 2024) 0 (1) 2024/11/15 11:25
[syzbot] Monthly kernfs report (Oct 2024) 0 (1) 2024/10/15 10:07
[syzbot] [kernfs?] INFO: task hung in fdget_pos 0 (2) 2024/10/12 15:45
Last patch testing requests (7)
Created Duration User Patch Repo Result
2025/06/25 12:56 41m retest repro upstream OK log
2025/04/24 00:13 25m retest repro upstream OK log
2025/04/22 11:20 20m retest repro upstream OK log
2025/02/04 08:42 16m retest repro upstream report log
2025/02/04 08:40 24m retest repro linux-next OK log
2025/02/04 08:43 18m retest repro upstream report log
2025/02/04 08:42 16m retest repro upstream report log

Sample crash report:
INFO: task syz.8.498:10221 blocked for more than 143 seconds.
      Not tainted 6.16.0-rc4-syzkaller-00123-g4c06e63b9203 #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.8.498       state:D stack:28904 pid:10221 tgid:10188 ppid:9011   task_flags:0x400040 flags:0x00004004
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5396 [inline]
 __schedule+0x16a2/0x4cb0 kernel/sched/core.c:6785
 __schedule_loop kernel/sched/core.c:6863 [inline]
 schedule+0x165/0x360 kernel/sched/core.c:6878
 schedule_preempt_disabled+0x13/0x30 kernel/sched/core.c:6935
 __mutex_lock_common kernel/locking/mutex.c:679 [inline]
 __mutex_lock+0x724/0xe80 kernel/locking/mutex.c:747
 fdget_pos+0x247/0x320 fs/file.c:1217
 class_fd_pos_constructor include/linux/file.h:85 [inline]
 ksys_read+0x79/0x250 fs/read_write.c:706
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fc62838e929
RSP: 002b:00007fc629188038 EFLAGS: 00000246 ORIG_RAX: 0000000000000000
RAX: ffffffffffffffda RBX: 00007fc6285b6160 RCX: 00007fc62838e929
RDX: 0000000000002020 RSI: 0000200000009800 RDI: 0000000000000006
RBP: 00007fc628410b39 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000001 R14: 00007fc6285b6160 R15: 00007ffe8e415768
 </TASK>

Showing all locks held in the system:
1 lock held by khungtaskd/31:
 #0: ffffffff8e13ee20 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:331 [inline]
 #0: ffffffff8e13ee20 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:841 [inline]
 #0: ffffffff8e13ee20 (rcu_read_lock){....}-{1:3}, at: debug_show_all_locks+0x2e/0x180 kernel/locking/lockdep.c:6770
5 locks held by kworker/u8:2/36:
4 locks held by kworker/u8:6/1104:
2 locks held by getty/5602:
 #0: ffff88814ceb80a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:243
 #1: ffffc9000332e2f0 (&ldata->atomic_read_lock){+.+.}-{4:4}, at: n_tty_read+0x43e/0x1400 drivers/tty/n_tty.c:2222
3 locks held by udevd/5857:
1 lock held by syz.8.498/10189:
 #0: ffff8880784b8428 (sb_writers#19){.+.+}-{0:0}, at: file_start_write include/linux/fs.h:3096 [inline]
 #0: ffff8880784b8428 (sb_writers#19){.+.+}-{0:0}, at: vfs_write+0x211/0xa90 fs/read_write.c:682
2 locks held by syz.8.498/10219:
 #0: ffff888030356d38 (&f->f_pos_lock){+.+.}-{4:4}, at: fdget_pos+0x247/0x320 fs/file.c:1217
 #1: ffff8880784b8428 (sb_writers#19){.+.+}-{0:0}, at: file_start_write include/linux/fs.h:3096 [inline]
 #1: ffff8880784b8428 (sb_writers#19){.+.+}-{0:0}, at: vfs_write+0x211/0xa90 fs/read_write.c:682
1 lock held by syz.8.498/10221:
 #0: ffff888030356d38 (&f->f_pos_lock){+.+.}-{4:4}, at: fdget_pos+0x247/0x320 fs/file.c:1217
2 locks held by syz.3.503/10492:
 #0: ffff8880784b80e0 (&type->s_umount_key#70){++++}-{4:4}, at: __super_lock fs/super.c:59 [inline]
 #0: ffff8880784b80e0 (&type->s_umount_key#70){++++}-{4:4}, at: super_lock+0x2a9/0x3b0 fs/super.c:121
 #1: ffff8880784b8950 (&s->s_sync_lock){+.+.}-{4:4}, at: wait_sb_inodes fs/fs-writeback.c:2653 [inline]
 #1: ffff8880784b8950 (&s->s_sync_lock){+.+.}-{4:4}, at: sync_inodes_sb+0x255/0xa10 fs/fs-writeback.c:2836
2 locks held by syz.8.589/11566:
 #0: ffff8880784b80e0 (&type->s_umount_key#70){++++}-{4:4}, at: __super_lock fs/super.c:59 [inline]
 #0: ffff8880784b80e0 (&type->s_umount_key#70){++++}-{4:4}, at: super_lock+0x2a9/0x3b0 fs/super.c:121
 #1: ffff8880784b8950 (&s->s_sync_lock){+.+.}-{4:4}, at: wait_sb_inodes fs/fs-writeback.c:2653 [inline]
 #1: ffff8880784b8950 (&s->s_sync_lock){+.+.}-{4:4}, at: sync_inodes_sb+0x255/0xa10 fs/fs-writeback.c:2836
1 lock held by syz.1.656/12615:
3 locks held by syz.7.653/12618:
 #0: ffff888022d818b0 (&bdev->bd_fsfreeze_mutex){+.+.}-{4:4}, at: bdev_freeze+0x2a/0x220 block/bdev.c:289
 #1: ffff88804871e428 (sb_writers#15){++++}-{0:0}, at: sb_wait_write fs/super.c:1900 [inline]
 #1: ffff88804871e428 (sb_writers#15){++++}-{0:0}, at: freeze_super+0x4db/0x1130 fs/super.c:2164
 #2: ffffffff8e144938 (rcu_state.exp_mutex){+.+.}-{4:4}, at: exp_funnel_lock kernel/rcu/tree_exp.h:336 [inline]
 #2: ffffffff8e144938 (rcu_state.exp_mutex){+.+.}-{4:4}, at: synchronize_rcu_expedited+0x3b9/0x730 kernel/rcu/tree_exp.h:998
2 locks held by syz.7.653/12648:
1 lock held by sed/12647:

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

NMI backtrace for cpu 0
CPU: 0 UID: 0 PID: 31 Comm: khungtaskd Not tainted 6.16.0-rc4-syzkaller-00123-g4c06e63b9203 #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/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:307 [inline]
 watchdog+0xfee/0x1030 kernel/hung_task.c:470
 kthread+0x711/0x8a0 kernel/kthread.c:464
 ret_from_fork+0x3fc/0x770 arch/x86/kernel/process.c:148
 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: 66 Comm: kworker/u8:4 Not tainted 6.16.0-rc4-syzkaller-00123-g4c06e63b9203 #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
Workqueue: bat_events batadv_nc_worker
RIP: 0010:arch_atomic_read arch/x86/include/asm/atomic.h:23 [inline]
RIP: 0010:raw_atomic_read include/linux/atomic/atomic-arch-fallback.h:457 [inline]
RIP: 0010:rcu_is_watching_curr_cpu include/linux/context_tracking.h:128 [inline]
RIP: 0010:rcu_is_watching+0x5a/0xb0 kernel/rcu/tree.c:745
Code: f0 48 c1 e8 03 42 80 3c 38 00 74 08 4c 89 f7 e8 0c 93 7a 00 48 c7 c3 58 1f 9e 92 49 03 1e 48 89 d8 48 c1 e8 03 42 0f b6 04 38 <84> c0 75 34 8b 03 65 ff 0d 79 cd f5 10 74 11 83 e0 04 c1 e8 02 5b
RSP: 0000:ffffc9000214fa00 EFLAGS: 00000a06
RAX: 0000000000000000 RBX: ffff8880b8732f58 RCX: 0adcfb96c931d200
RDX: ffff88801cf29e00 RSI: ffffffff8be1bc20 RDI: ffffffff8be1bbe0
RBP: ffff8880404e5410 R08: 0000000000000000 R09: ffffffff8b360122
R10: dffffc0000000000 R11: ffffffff8b360050 R12: dffffc0000000000
R13: ffffffff8b360122 R14: ffffffff8dba8c68 R15: dffffc0000000000
FS:  0000000000000000(0000) GS:ffff888125d51000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fcf5f9dd000 CR3: 0000000033e08000 CR4: 00000000003526f0
Call Trace:
 <TASK>
 rcu_read_lock include/linux/rcupdate.h:842 [inline]
 batadv_nc_purge_orig_hash net/batman-adv/network-coding.c:408 [inline]
 batadv_nc_worker+0x10c/0x610 net/batman-adv/network-coding.c:719
 process_one_work kernel/workqueue.c:3238 [inline]
 process_scheduled_works+0xae1/0x17b0 kernel/workqueue.c:3321
 worker_thread+0x8a0/0xda0 kernel/workqueue.c:3402
 kthread+0x711/0x8a0 kernel/kthread.c:464
 ret_from_fork+0x3fc/0x770 arch/x86/kernel/process.c:148
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
 </TASK>

Crashes (101):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/07/04 21:39 upstream 4c06e63b9203 d869b261 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in fdget_pos
2025/07/01 03:49 upstream 66701750d556 6e83b42d .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in fdget_pos
2025/06/29 19:27 upstream afa9a6f4f574 fc9d8ee5 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in fdget_pos
2025/06/29 14:43 upstream dfba48a70cb6 fc9d8ee5 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in fdget_pos
2025/06/10 04:42 upstream 19272b37aa4f 4826c28e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in fdget_pos
2025/05/17 03:13 upstream 3c21441eeffc f41472b0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in fdget_pos
2025/05/07 10:19 upstream 0d8d44db295c 350f4ffc .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in fdget_pos
2025/05/07 06:14 upstream 0d8d44db295c 350f4ffc .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in fdget_pos
2025/05/05 03:50 upstream 14c55b7bb0a8 b0714e37 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in fdget_pos
2025/05/02 04:22 upstream ebd297a2affa 51b137cd .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in fdget_pos
2025/04/28 20:56 upstream f15d97df5afa aeb6ec69 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in fdget_pos
2025/04/08 10:54 upstream 0af2f6be1b42 a775275d .config console log report info [disk image] [vmlinux] [kernel image] ci-qemu-gce-upstream-auto INFO: task hung in fdget_pos
2025/01/21 08:35 upstream 3d3a9c8b89d4 6e87cfa2 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in fdget_pos
2025/01/19 15:46 upstream fda5e3f28400 f2cb035c .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in fdget_pos
2025/01/05 07:02 upstream ab75170520d4 f3558dbf .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in fdget_pos
2024/12/29 14:55 upstream 059dd502b263 d3ccff63 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in fdget_pos
2024/12/27 13:27 upstream d6ef8b40d075 d3ccff63 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in fdget_pos
2024/12/26 13:23 upstream 9b2ffa6148b1 d3ccff63 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in fdget_pos
2024/12/25 09:20 upstream 9b2ffa6148b1 444551c4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in fdget_pos
2024/12/16 21:34 upstream 78d4f34e2115 f93b2b55 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in fdget_pos
2024/12/10 19:25 upstream 7cb1b4663150 cfc402b4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in fdget_pos
2024/12/03 06:22 upstream cdd30ebb1b9f 578925bc .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in fdget_pos
2024/11/30 23:58 upstream 2ba9f676d0a2 68914665 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in fdget_pos
2024/11/24 23:09 upstream 9f16d5e6f220 68da6d95 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in fdget_pos
2024/11/23 22:27 upstream 228a1157fb9f 68da6d95 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in fdget_pos
2024/11/23 15:06 upstream 228a1157fb9f 68da6d95 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in fdget_pos
2024/11/22 19:17 upstream 28eb75e178d3 4b25d554 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in fdget_pos
2024/11/11 06:12 upstream a9cda7c0ffed 6b856513 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in fdget_pos
2024/11/08 15:53 upstream 906bd684e4b1 179b040e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in fdget_pos
2024/11/08 13:59 upstream 906bd684e4b1 179b040e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in fdget_pos
2024/11/08 09:54 upstream 906bd684e4b1 179b040e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in fdget_pos
2024/11/08 06:18 upstream 906bd684e4b1 179b040e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in fdget_pos
2024/11/07 02:02 upstream 7758b206117d df3dc63b .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in fdget_pos
2024/11/05 06:00 upstream 557329bcecc2 509da429 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in fdget_pos
2024/10/21 22:18 upstream d12937763990 f1e4447c .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in fdget_pos
2024/10/20 16:46 upstream 715ca9dd687f cd6fc0a3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in fdget_pos
2024/10/20 01:32 upstream f9e4825524aa cd6fc0a3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in fdget_pos
2024/10/19 02:42 upstream b04ae0f45168 cd6fc0a3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in fdget_pos
2024/10/14 14:06 upstream 6485cf5ea253 084d8178 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in fdget_pos
2024/10/06 06:32 upstream fc20a3e57247 d7906eff .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in fdget_pos
2024/09/28 12:09 upstream ad46e8f95e93 ba29ff75 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in fdget_pos
2024/10/12 15:44 upstream 09f6b0c8904b 084d8178 .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 fdget_pos
2025/07/04 11:04 linux-next 8d6c58332c7a 76ad128c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in fdget_pos
2025/01/13 01:15 linux-next 7b4b9bf203da 6dbc6a9b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in fdget_pos
2024/11/12 15:53 linux-next 929beafbe7ac 75bb1b32 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-linux-next-kasan-gce-root INFO: task hung in fdget_pos
2024/10/31 20:39 linux-next f9f24ca362a4 96eb609f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in fdget_pos
2025/03/03 04:54 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci e056da87c780 c3901742 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 INFO: task hung in fdget_pos
2024/10/24 19:01 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci ce8e69898653 9fc8fe02 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 INFO: task hung in fdget_pos
2024/10/23 17:12 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 fdget_pos
2024/10/21 09:00 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 9ec59cb3edc7 cd6fc0a3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 INFO: task hung in fdget_pos
2024/10/19 20:22 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci d2b1b3bccef6 cd6fc0a3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 INFO: task hung in fdget_pos
2024/10/19 15:07 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci d2b1b3bccef6 cd6fc0a3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 INFO: task hung in fdget_pos
2024/10/19 06:53 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci d2b1b3bccef6 cd6fc0a3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 INFO: task hung in fdget_pos
* Struck through repros no longer work on HEAD.