syzbot


INFO: task hung in kernfs_notify_workfn (3)

Status: auto-obsoleted due to no activity on 2026/05/17 04:02
Subsystems: kernfs
[Documentation on labels]
First crash: 400d, last: 125d
✨ AI Jobs (2)
ID Workflow Result Correct Bug Created Started Finished Revision Error
60b71134-d5ff-4114-b3ba-85bd636a24d5 assessment-security 💥 INFO: task hung in kernfs_notify_workfn (3) 2026/05/15 07:27 2026/05/15 07:27 2026/05/15 07:28 6ccb967e465e832a7bfd7a116ad00d52a0923a5d
failed to run ["git" "pull" "origin" "HEAD" "--depth=1" "--allow-unrelated-histories"]: exit status 128
From /app/workdir/repo/linux
 * branch                HEAD       -> FETCH_HEAD
error: unable to ...
truncated to first 200 bytes; open job for full error
c72356f3-ec38-4a56-9bfc-f169deb56fcb repro INFO: task hung in kernfs_notify_workfn (3) 2026/03/07 07:33 2026/03/07 07:33 2026/03/07 07:40 31e9c887f7dc24e04b3ca70d0d54fc34141844b0

			
		
Similar bugs (3)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream INFO: task hung in kernfs_notify_workfn (2) kernfs 1 1 2347d 2347d 0/29 auto-closed as invalid on 2020/04/16 13:34
upstream INFO: task hung in kernfs_notify_workfn kernfs 1 3 2515d 2519d 0/29 auto-closed as invalid on 2019/10/31 10:51
linux-4.19 INFO: task hung in kernfs_notify_workfn 1 1 2277d 2277d 0/1 auto-closed as invalid on 2020/07/25 12:09

Sample crash report:
INFO: task kworker/0:1:10 blocked for more than 143 seconds.
      Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/0:1     state:R
  running task    
 stack:22168 pid:10    tgid:10    ppid:2      task_flags:0x4208060 flags:0x00080000
Workqueue: events kernfs_notify_workfn

Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5260 [inline]
 __schedule+0xeb0/0x3e50 kernel/sched/core.c:6867
 __schedule_loop kernel/sched/core.c:6949 [inline]
 schedule+0xdd/0x390 kernel/sched/core.c:6964
 schedule_preempt_disabled+0x13/0x30 kernel/sched/core.c:7021
 rwsem_down_read_slowpath+0x5dc/0xb30 kernel/locking/rwsem.c:1086
 __down_read_common kernel/locking/rwsem.c:1261 [inline]
 __down_read kernel/locking/rwsem.c:1274 [inline]
 down_read+0xed/0x460 kernel/locking/rwsem.c:1539
 kernfs_notify_workfn+0xff/0x5f0 fs/kernfs/file.c:933
 process_one_work+0x9c2/0x1840 kernel/workqueue.c:3257
 process_scheduled_works kernel/workqueue.c:3340 [inline]
 worker_thread+0x5da/0xe40 kernel/workqueue.c:3421
 kthread+0x3b3/0x730 kernel/kthread.c:463
 ret_from_fork+0x6c3/0xa20 arch/x86/kernel/process.c:158
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:246
 </TASK>
INFO: task kworker/1:0:23 blocked for more than 143 seconds.
      Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/1:0     state:D stack:24232 pid:23    tgid:23    ppid:2      task_flags:0x4208060 flags:0x00080000
Workqueue: usb_hub_wq hub_event

Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5260 [inline]
 __schedule+0xeb0/0x3e50 kernel/sched/core.c:6867
 </TASK>

Showing all locks held in the system:
2 locks held by kworker/0:0/9:
4 locks held by kworker/0:1/10:
 #0: ffff888100071948 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x11ae/0x1840 kernel/workqueue.c:3232
 #1: ffffc900000afca8 (kernfs_notify_work){+.+.}-{0:0}, at: process_one_work+0x927/0x1840 kernel/workqueue.c:3233
 #2: ffff888100ac5ab8 (&root->kernfs_supers_rwsem){++++}-{4:4}, at: kernfs_notify_workfn+0xf7/0x5f0 fs/kernfs/file.c:932
 #3: ffff888100ac5988 (&root->kernfs_rwsem){++++}-{4:4}, at: kernfs_notify_workfn+0xff/0x5f0 fs/kernfs/file.c:933
7 locks held by kworker/1:0/23:
 #0: ffff888100ed2d48 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: process_one_work+0x11ae/0x1840 kernel/workqueue.c:3232
 #1: ffffc9000018fca8 ((work_completion)(&hub->events)){+.+.}-{0:0}, at: process_one_work+0x927/0x1840 kernel/workqueue.c:3233
 #2: ffff88810a3b1198 (&dev->mutex){....}-{4:4}, at: device_lock include/linux/device.h:895 [inline]
 #2: ffff88810a3b1198 (&dev->mutex){....}-{4:4}, at: hub_event+0x1bd/0x4af0 drivers/usb/core/hub.c:5899
 #3: ffff888104ad0198 (&dev->mutex){....}-{4:4}, at: device_lock include/linux/device.h:895 [inline]
 #3: ffff888104ad0198 (&dev->mutex){....}-{4:4}, at: usb_disconnect+0x10a/0x9a0 drivers/usb/core/hub.c:2336
 #4: ffff88811b509160 (&dev->mutex){....}-{4:4}, at: device_lock include/linux/device.h:895 [inline]
 #4: ffff88811b509160 (&dev->mutex){....}-{4:4}, at: __device_driver_lock drivers/base/dd.c:1104 [inline]
 #4: ffff88811b509160 (&dev->mutex){....}-{4:4}, at: device_release_driver_internal+0xaa/0x600 drivers/base/dd.c:1302
 #5: ffffffff8a2e1068 (input_mutex){+.+.}-{4:4}, at: class_mutex_constructor include/linux/mutex.h:253 [inline]
 #5: ffffffff8a2e1068 (input_mutex){+.+.}-{4:4}, at: __input_unregister_device+0x184/0x4d0 drivers/input/input.c:2187
 #6: ffff888100ac5988 (&root->kernfs_rwsem){++++}-{4:4}, at: kernfs_remove_by_name_ns+0x3d/0xf0 fs/kernfs/dir.c:1717
1 lock held by khungtaskd/30:
 #0: ffffffff894da3a0 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:331 [inline]
 #0: ffffffff894da3a0 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:867 [inline]
 #0: ffffffff894da3a0 (rcu_read_lock){....}-{1:3}, at: debug_show_all_locks+0x3d/0x184 kernel/locking/lockdep.c:6775
5 locks held by kworker/1:1/38:
 #0: ffff888100ed2d48 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: process_one_work+0x11ae/0x1840 kernel/workqueue.c:3232
 #1: ffffc90000287ca8 ((work_completion)(&hub->events)){+.+.}-{0:0}, at: process_one_work+0x927/0x1840 kernel/workqueue.c:3233
 #2: ffff88810a399198 (&dev->mutex){....}-{4:4}, at: device_lock include/linux/device.h:895 [inline]
 #2: ffff88810a399198 (&dev->mutex){....}-{4:4}, at: hub_event+0x1bd/0x4af0 drivers/usb/core/hub.c:5899
 #3: ffff888123e42198 (&dev->mutex){....}-{4:4}, at: device_lock include/linux/device.h:895 [inline]
 #3: ffff888123e42198 (&dev->mutex){....}-{4:4}, at: usb_disconnect+0x10a/0x9a0 drivers/usb/core/hub.c:2336
 #4: ffff888100ac5988 (&root->kernfs_rwsem){++++}-{4:4}, at: kernfs_remove_by_name_ns+0x3d/0xf0 fs/kernfs/dir.c:1717
4 locks held by kworker/u8:6/167:
 #0: ffff888100ac4948 ((wq_completion)netns){+.+.}-{0:0}, at: process_one_work+0x11ae/0x1840 kernel/workqueue.c:3232
 #1: ffffc9000154fca8 (net_cleanup_work){+.+.}-{0:0}, at: process_one_work+0x927/0x1840 kernel/workqueue.c:3233
 #2: ffffffff8a8b4af0 (pernet_ops_rwsem){++++}-{4:4}, at: cleanup_net+0xab/0x900 net/core/net_namespace.c:670
 #3: ffffffff894e6a40 (rcu_state.barrier_mutex){+.+.}-{4:4}, at: rcu_barrier+0x48/0x6d0 kernel/rcu/tree.c:3816
6 locks held by kworker/0:2/1123:
 #0: ffff888100ed2d48 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: process_one_work+0x11ae/0x1840 kernel/workqueue.c:3232
 #1: ffffc90001d6fca8 ((work_completion)(&hub->events)){+.+.}-{0:0}, at: process_one_work+0x927/0x1840 kernel/workqueue.c:3233
 #2: ffff88810a751198 (&dev->mutex){....}-{4:4}, at: device_lock include/linux/device.h:895 [inline]
 #2: ffff88810a751198 (&dev->mutex){....}-{4:4}, at: hub_event+0x1bd/0x4af0 drivers/usb/core/hub.c:5899
 #3: ffff88811b451198 (&dev->mutex){....}-{4:4}, at: device_lock include/linux/device.h:895 [inline]
 #3: ffff88811b451198 (&dev->mutex){....}-{4:4}, at: usb_disconnect+0x10a/0x9a0 drivers/usb/core/hub.c:2336
 #4: ffff888105efc278 (&(&priv->bus_notifier)->rwsem){++++}-{4:4}, at: blocking_notifier_call_chain kernel/notifier.c:379 [inline]
 #4: ffff888105efc278 (&(&priv->bus_notifier)->rwsem){++++}-{4:4}, at: blocking_notifier_call_chain+0x53/0xa0 kernel/notifier.c:368
 #5: ffff888100ac5988 (&root->kernfs_rwsem){++++}-{4:4}, at: kernfs_remove_by_name_ns+0x3d/0xf0 fs/kernfs/dir.c:1717
1 lock held by udevd/2860:
 #0: ffff888100ac5988 (&root->kernfs_rwsem){++++}-{4:4}, at: kernfs_dop_revalidate+0xa5/0x740 fs/kernfs/dir.c:1185
2 locks held by getty/2924:
 #0: ffff888115ca80a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x24/0x80 drivers/tty/tty_ldisc.c:243
 #1: ffffc900000452f0 (&ldata->atomic_read_lock){+.+.}-{4:4}, at: n_tty_read+0x419/0x1500 drivers/tty/n_tty.c:2211
4 locks held by kworker/1:2/5220:
2 locks held by udevd/5232:
 #0: ffff888119086408 (&type->i_mutex_dir_key#4){++++}-{4:4}, at: inode_lock_shared include/linux/fs.h:1042 [inline]
 #0: ffff888119086408 (&type->i_mutex_dir_key#4){++++}-{4:4}, at: lookup_slow+0x42/0x70 fs/namei.c:1882
 #1: ffff888100ac5988 (&root->kernfs_rwsem){++++}-{4:4}, at: kernfs_iop_lookup+0x5b/0x2d0 fs/kernfs/dir.c:1227
1 lock held by udevd/5234:
 #0: ffff888100ac5988 (&root->kernfs_rwsem){++++}-{4:4}, at: kernfs_dop_revalidate+0xa5/0x740 fs/kernfs/dir.c:1185
1 lock held by syz.3.25/5300:
 #0: ffff888100ac5988 (&root->kernfs_rwsem){++++}-{4:4}, at: kernfs_activate fs/kernfs/dir.c:1430 [inline]
 #0: ffff888100ac5988 (&root->kernfs_rwsem){++++}-{4:4}, at: kernfs_add_one+0x54f/0x850 fs/kernfs/dir.c:839
1 lock held by syz.4.26/5304:
 #0: ffff888100ac5988 (&root->kernfs_rwsem){++++}-{4:4}, at: kernfs_activate fs/kernfs/dir.c:1430 [inline]
 #0: ffff888100ac5988 (&root->kernfs_rwsem){++++}-{4:4}, at: kernfs_add_one+0x54f/0x850 fs/kernfs/dir.c:839
2 locks held by syz.1.27/5306:
 #0: ffff88810a310dc0 (&dev->mutex){....}-{4:4}, at: device_lock include/linux/device.h:895 [inline]
 #0: ffff88810a310dc0 (&dev->mutex){....}-{4:4}, at: __device_driver_lock drivers/base/dd.c:1104 [inline]
 #0: ffff88810a310dc0 (&dev->mutex){....}-{4:4}, at: __driver_attach+0x20c/0x5c0 drivers/base/dd.c:1224
 #1: ffff888100ac5988 (&root->kernfs_rwsem){++++}-{4:4}, at: kernfs_add_one+0x38/0x850 fs/kernfs/dir.c:796
1 lock held by syz.0.28/5308:
1 lock held by syz-executor/5310:
1 lock held by syz-executor/5311:
 #0: ffff888100ac5988 (&root->kernfs_rwsem){++++}-{4:4}, at: kernfs_dop_revalidate+0xa5/0x740 fs/kernfs/dir.c:1185
1 lock held by syz-executor/5313:
 #0: ffff888100ac5988 (&root->kernfs_rwsem){++++}-{4:4}, at: kernfs_dop_revalidate+0xa5/0x740 fs/kernfs/dir.c:1185

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

NMI backtrace for cpu 1
CPU: 1 UID: 0 PID: 30 Comm: khungtaskd Not tainted syzkaller #0 PREEMPT(voluntary) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2026
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:94 [inline]
 dump_stack_lvl+0x100/0x190 lib/dump_stack.c:120
 nmi_cpu_backtrace.cold+0x12d/0x151 lib/nmi_backtrace.c:113
 nmi_trigger_cpumask_backtrace+0x1d7/0x230 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:161 [inline]
 __sys_info lib/sys_info.c:157 [inline]
 sys_info+0x141/0x190 lib/sys_info.c:165
 check_hung_uninterruptible_tasks kernel/hung_task.c:346 [inline]
 watchdog+0xcc3/0xfe0 kernel/hung_task.c:515
 kthread+0x3b3/0x730 kernel/kthread.c:463
 ret_from_fork+0x6c3/0xa20 arch/x86/kernel/process.c:158
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:246
 </TASK>
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 UID: 0 PID: 5310 Comm: syz-executor Not tainted syzkaller #0 PREEMPT(voluntary) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2026
RIP: 0010:bytes_is_nonzero mm/kasan/generic.c:97 [inline]
RIP: 0010:memory_is_nonzero mm/kasan/generic.c:115 [inline]
RIP: 0010:memory_is_poisoned_n mm/kasan/generic.c:140 [inline]
RIP: 0010:memory_is_poisoned mm/kasan/generic.c:172 [inline]
RIP: 0010:check_region_inline mm/kasan/generic.c:191 [inline]
RIP: 0010:kasan_check_range+0x161/0x1e0 mm/kasan/generic.c:200
Code: 48 39 d0 74 0f 80 38 00 74 ef 4e 8d 5c 25 00 48 85 c0 75 9d 48 89 da 4c 89 d8 4c 29 da e9 32 ff ff ff 48 85 d2 74 98 48 01 ea <eb> 1a 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 48 83 c0 01 48 39 d0
RSP: 0018:ffffc900018975d0 EFLAGS: 00000282
RAX: fffff940009d91f6 RBX: fffff940009d91f7 RCX: ffffffff81fdb887
RDX: fffff940009d91f7 RSI: 0000000000000004 RDI: ffffea0004ec8fb0
RBP: fffff940009d91f6 R08: 0000000000000000 R09: fffff940009d91f6
R10: ffffea0004ec8fb3 R11: 0000000000000000 R12: 0000000000000000
R13: dffffc0000000000 R14: 800000013b23e027 R15: ffff888124098500
FS:  0000000000000000(0000) GS:ffff88826896a000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fa46a576038 CR3: 00000000092a8000 CR4: 00000000003506f0
Call Trace:
 <TASK>
 instrument_atomic_read include/linux/instrumented.h:68 [inline]
 atomic_read include/linux/atomic/atomic-instrumented.h:32 [inline]
 folio_mapcount include/linux/mm.h:1394 [inline]
 zap_present_folio_ptes mm/memory.c:1652 [inline]
 zap_present_ptes mm/memory.c:1708 [inline]
 do_zap_pte_range mm/memory.c:1810 [inline]
 zap_pte_range mm/memory.c:1854 [inline]
 zap_pmd_range mm/memory.c:1946 [inline]
 zap_pud_range mm/memory.c:1975 [inline]
 zap_p4d_range mm/memory.c:1996 [inline]
 unmap_page_range+0x17a7/0x39e0 mm/memory.c:2017
 unmap_single_vma+0x153/0x240 mm/memory.c:2059
 unmap_vmas+0x218/0x470 mm/memory.c:2101
 exit_mmap+0x181/0xae0 mm/mmap.c:1277
 __mmput kernel/fork.c:1173 [inline]
 mmput+0xe0/0x430 kernel/fork.c:1196
 exit_mm kernel/exit.c:581 [inline]
 do_exit+0x78a/0x2a30 kernel/exit.c:959
 do_group_exit+0xd5/0x2a0 kernel/exit.c:1112
 get_signal+0x1ec7/0x21e0 kernel/signal.c:3034
 arch_do_signal_or_restart+0x91/0x7a0 arch/x86/kernel/signal.c:337
 __exit_to_user_mode_loop kernel/entry/common.c:41 [inline]
 exit_to_user_mode_loop+0x7e/0x430 kernel/entry/common.c:75
 __exit_to_user_mode_prepare include/linux/irq-entry-common.h:226 [inline]
 syscall_exit_to_user_mode_prepare include/linux/irq-entry-common.h:256 [inline]
 syscall_exit_to_user_mode_work include/linux/entry-common.h:159 [inline]
 syscall_exit_to_user_mode include/linux/entry-common.h:194 [inline]
 do_syscall_64+0x4a8/0x570 arch/x86/entry/syscall_64.c:100
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7eff5cf0bce2
Code: Unable to access opcode bytes at 0x7eff5cf0bcb8.
RSP: 002b:00007ffdd7c36288 EFLAGS: 00000206 ORIG_RAX: 0000000000000009
RAX: 00007eff5c565000 RBX: 00007eff5c565000 RCX: 00007eff5cf0bce2
RDX: 0000000000000003 RSI: 0000000000400000 RDI: 00007eff5c565000
RBP: 0000000000000011 R08: 00000000000000d9 R09: 0000000000000000
R10: 0000000000000011 R11: 0000000000000206 R12: 0000000000000003
R13: 0000000000000003 R14: 00007ffdd7c364f8 R15: 0000000000000000
 </TASK>

Crashes (8):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/02/16 03:52 https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-testing da87d45b1951 1e62d198 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-usb INFO: task hung in kernfs_notify_workfn
2025/12/27 00:50 https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-testing 8995a37371bf d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-usb INFO: task hung in kernfs_notify_workfn
2025/10/07 15:19 https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-testing c746c3b51698 8ef35d49 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-usb INFO: task hung in kernfs_notify_workfn
2025/09/23 07:34 https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-testing a4e143636d5d 0ac7291c .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-usb INFO: task hung in kernfs_notify_workfn
2025/07/24 14:04 https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-testing 8d1b02e5d7e3 65d60d73 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-usb INFO: task hung in kernfs_notify_workfn
2025/07/21 09:51 https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-testing a83c371c4b6c 7117feec .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-usb INFO: task hung in kernfs_notify_workfn
2025/06/17 04:38 https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-testing e04c78d86a96 cfebc887 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-usb INFO: task hung in kernfs_notify_workfn
2025/05/16 14:26 https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-testing ab6dc9a6c721 cfde8269 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-usb INFO: task hung in kernfs_notify_workfn
* Struck through repros no longer work on HEAD.