[v6.1] INFO: task hung in block_invalidate_folio (2)
0 views
Skip to first unread message
syzbot
Feb 13, 2026, 7:20:43 PM (2 days ago) Feb 13
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 8ce36b2849ef Linux 6.1.163
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=17fe415a580000
kernel config: https://syzkaller.appspot.com/x/.config?x=f0605c5af04d7603
dashboard link: https://syzkaller.appspot.com/bug?extid=ae150307c18be27c9a06
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/25d3bb1313db/disk-8ce36b28.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/53d3c77e16da/vmlinux-8ce36b28.xz
kernel image: https://storage.googleapis.com/syzbot-assets/ca171a78e481/bzImage-8ce36b28.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+ae1503...@syzkaller.appspotmail.com
INFO: task kworker/0:1H:52 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:1H state:D stack:25872 pid:52 ppid:2 flags:0x00004000
Workqueue: glock_workqueue glock_work_func
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5245 [inline]
__schedule+0x11d1/0x40e0 kernel/sched/core.c:6562
schedule+0xb9/0x180 kernel/sched/core.c:6638
io_schedule+0x7c/0xd0 kernel/sched/core.c:8798
bit_wait_io+0xd/0xc0 kernel/sched/wait_bit.c:209
__wait_on_bit_lock+0xd8/0x580 kernel/sched/wait_bit.c:90
out_of_line_wait_on_bit_lock+0x138/0x190 kernel/sched/wait_bit.c:117
wait_on_bit_lock_io include/linux/wait_bit.h:208 [inline]
__lock_buffer fs/buffer.c:69 [inline]
lock_buffer include/linux/buffer_head.h:397 [inline]
discard_buffer fs/buffer.c:1458 [inline]
block_invalidate_folio+0x37b/0x9e0 fs/buffer.c:1515
folio_invalidate mm/truncate.c:158 [inline]
truncate_cleanup_folio+0x218/0x5e0 mm/truncate.c:178
truncate_inode_pages_range+0x293/0x1090 mm/truncate.c:393
do_xmote+0x50a/0x13c0 fs/gfs2/glock.c:801
glock_work_func+0x25e/0x470 fs/gfs2/glock.c:1089
process_one_work+0x8a2/0x1160 kernel/workqueue.c:2292
worker_thread+0xaa2/0x1270 kernel/workqueue.c:2439
kthread+0x29d/0x330 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
</TASK>
INFO: task syz-executor:16118 blocked for more than 144 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor state:D stack:20656 pid:16118 ppid:1 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5245 [inline]
__schedule+0x11d1/0x40e0 kernel/sched/core.c:6562
schedule+0xb9/0x180 kernel/sched/core.c:6638
schedule_timeout+0xbd/0x2d0 kernel/time/timer.c:2144
do_wait_for_common kernel/sched/completion.c:85 [inline]
__wait_for_common kernel/sched/completion.c:106 [inline]
wait_for_common kernel/sched/completion.c:117 [inline]
wait_for_completion+0x2c7/0x5a0 kernel/sched/completion.c:138
__flush_work+0x952/0xae0 kernel/workqueue.c:3076
flush_work kernel/workqueue.c:3097 [inline]
flush_delayed_work+0x12d/0x180 kernel/workqueue.c:3221
gfs2_clear_rgrpd+0xd3/0x6d0 fs/gfs2/rgrp.c:731
gfs2_put_super+0x844/0x8c0 fs/gfs2/super.c:638
generic_shutdown_super+0x130/0x340 fs/super.c:501
kill_block_super+0x7c/0xe0 fs/super.c:1470
deactivate_locked_super+0x93/0xf0 fs/super.c:332
cleanup_mnt+0x42c/0x4b0 fs/namespace.c:1191
task_work_run+0x1d0/0x260 kernel/task_work.c:203
resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
exit_to_user_mode_loop+0xe6/0x110 kernel/entry/common.c:177
exit_to_user_mode_prepare+0xee/0x180 kernel/entry/common.c:210
__syscall_exit_to_user_mode_work kernel/entry/common.c:292 [inline]
syscall_exit_to_user_mode+0x16/0x40 kernel/entry/common.c:303
do_syscall_64+0x58/0xa0 arch/x86/entry/common.c:82
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7ff6d139d1d7
RSP: 002b:00007fff1c87f848 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 00007ff6d1431c3b RCX: 00007ff6d139d1d7
RDX: 0000000000000000 RSI: 0000000000000009 RDI: 00007fff1c87f900
RBP: 00007fff1c87f900 R08: 00007fff1c880900 R09: 00000000ffffffff
R10: 0000000000000000 R11: 0000000000000246 R12: 00007fff1c880990
R13: 00007ff6d1431c3b R14: 000000000019d0d1 R15: 00007fff1c8809d0
</TASK>
Showing all locks held in the system:
1 lock held by rcu_tasks_kthre/12:
#0: ffffffff8cb2dfb0 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x33/0xf00 kernel/rcu/tasks.h:517
1 lock held by rcu_tasks_trace/13:
#0: ffffffff8cb2e7d0 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x33/0xf00 kernel/rcu/tasks.h:517
1 lock held by khungtaskd/28:
#0: ffffffff8cb2d620 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:350 [inline]
#0: ffffffff8cb2d620 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:791 [inline]
#0: ffffffff8cb2d620 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x51/0x290 kernel/locking/lockdep.c:6513
2 locks held by kworker/0:1H/52:
#0: ffff888140f58538 ((wq_completion)glock_workqueue){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
#1: ffffc90000bd7d00 ((work_completion)(&(&gl->gl_work)->work)){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
2 locks held by getty/4026:
#0: ffff88814d5e4098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:244
#1: ffffc9000327b2f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x429/0x1390 drivers/tty/n_tty.c:2198
4 locks held by kworker/u4:7/4372:
#0: ffff888017616938 ((wq_completion)netns){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
#1: ffffc9000468fd00 (net_cleanup_work){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
#2: ffffffff8dd39450 (pernet_ops_rwsem){++++}-{3:3}, at: cleanup_net+0x148/0xba0 net/core/net_namespace.c:594
#3: ffffffff8dd46328 (rtnl_mutex){+.+.}-{3:3}, at: ieee80211_unregister_hw+0x51/0x290 net/mac80211/main.c:1476
3 locks held by kworker/u4:23/6238:
#0: ffff888017479138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
#1: ffffc9000360fd00 ((linkwatch_work).work){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
#2: ffffffff8dd46328 (rtnl_mutex){+.+.}-{3:3}, at: linkwatch_event+0xa/0x50 net/core/link_watch.c:263
2 locks held by kworker/1:14/9481:
#0: ffff888017472138 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
#1: ffffc9000c917d00 ((work_completion)(&rew->rew_work)){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
2 locks held by kworker/1:0/14470:
#0: ffff888017470938 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
#1: ffffc90005fc7d00 (free_ipc_work){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
1 lock held by syz-executor/16118:
#0: ffff888066b1c0e0 (&type->s_umount_key#92){+.+.}-{3:3}, at: deactivate_super+0xa0/0xd0 fs/super.c:362
3 locks held by kworker/0:5/17414:
#0: ffff88814d135d38 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
#1: ffffc90003397d00 ((work_completion)(&(&ifa->dad_work)->work)){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
#2: ffffffff8dd46328 (rtnl_mutex){+.+.}-{3:3}, at: addrconf_dad_work+0xca/0x14f0 net/ipv6/addrconf.c:4131
3 locks held by syz-executor/17810:
#0: ffff88801fbf10b8 (&hdev->req_lock){+.+.}-{3:3}, at: hci_dev_do_close net/bluetooth/hci_core.c:508 [inline]
#0: ffff88801fbf10b8 (&hdev->req_lock){+.+.}-{3:3}, at: hci_unregister_dev+0x1fa/0x4f0 net/bluetooth/hci_core.c:2705
#1: ffff88801fbf0078 (&hdev->lock){+.+.}-{3:3}, at: hci_dev_close_sync+0x458/0xf40 net/bluetooth/hci_sync.c:5233
#2: ffffffff8dea42e8 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_disconn_cfm include/net/bluetooth/hci_core.h:1826 [inline]
#2: ffffffff8dea42e8 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_conn_hash_flush+0xac/0x290 net/bluetooth/hci_conn.c:2504
3 locks held by syz.9.3319/18367:
#0: ffff8880617e10b8 (&hdev->req_lock){+.+.}-{3:3}, at: hci_dev_do_close net/bluetooth/hci_core.c:508 [inline]
#0: ffff8880617e10b8 (&hdev->req_lock){+.+.}-{3:3}, at: hci_unregister_dev+0x1fa/0x4f0 net/bluetooth/hci_core.c:2705
#1: ffff8880617e0078 (&hdev->lock){+.+.}-{3:3}, at: hci_dev_close_sync+0x458/0xf40 net/bluetooth/hci_sync.c:5233
#2: ffffffff8dea42e8 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_disconn_cfm include/net/bluetooth/hci_core.h:1826 [inline]
#2: ffffffff8dea42e8 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_conn_hash_flush+0xac/0x290 net/bluetooth/hci_conn.c:2504
2 locks held by syz.2.3352/18534:
#0: ffffffff8dd46328 (rtnl_mutex){+.+.}-{3:3}, at: tun_detach drivers/net/tun.c:698 [inline]
#0: ffffffff8dd46328 (rtnl_mutex){+.+.}-{3:3}, at: tun_chr_close+0x3d/0x1b0 drivers/net/tun.c:3492
#1: ffffffff8cb332f8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:323 [inline]
#1: ffffffff8cb332f8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x3c0/0x890 kernel/rcu/tree_exp.h:962
3 locks held by syz-executor/18793:
#0: ffff888063a9d0b8 (&hdev->req_lock){+.+.}-{3:3}, at: hci_dev_do_close net/bluetooth/hci_core.c:508 [inline]
#0: ffff888063a9d0b8 (&hdev->req_lock){+.+.}-{3:3}, at: hci_unregister_dev+0x1fa/0x4f0 net/bluetooth/hci_core.c:2705
#1: ffff888063a9c078 (&hdev->lock){+.+.}-{3:3}, at: hci_dev_close_sync+0x458/0xf40 net/bluetooth/hci_sync.c:5233
#2: ffffffff8dea42e8 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_disconn_cfm include/net/bluetooth/hci_core.h:1826 [inline]
#2: ffffffff8dea42e8 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_conn_hash_flush+0xac/0x290 net/bluetooth/hci_conn.c:2504
3 locks held by syz.8.3470/19120:
#0: ffff8880399ad0b8 (&hdev->req_lock){+.+.}-{3:3}, at: hci_dev_do_close net/bluetooth/hci_core.c:508 [inline]
#0: ffff8880399ad0b8 (&hdev->req_lock){+.+.}-{3:3}, at: hci_unregister_dev+0x1fa/0x4f0 net/bluetooth/hci_core.c:2705
#1: ffff8880399ac078 (&hdev->lock){+.+.}-{3:3}, at: hci_dev_close_sync+0x458/0xf40 net/bluetooth/hci_sync.c:5233
#2: ffffffff8cb332f8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:323 [inline]
#2: ffffffff8cb332f8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x3c0/0x890 kernel/rcu/tree_exp.h:962
=============================================
NMI backtrace for cpu 0
CPU: 0 PID: 28 Comm: khungtaskd Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/24/2026
Call Trace:
<TASK>
dump_stack_lvl+0x188/0x24e lib/dump_stack.c:106
nmi_cpu_backtrace+0x3e6/0x460 lib/nmi_backtrace.c:111
nmi_trigger_cpumask_backtrace+0x1d4/0x450 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:220 [inline]
watchdog+0xeee/0xf30 kernel/hung_task.c:377
kthread+0x29d/0x330 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
</TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 21 Comm: ksoftirqd/1 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/24/2026
RIP: 0010:memset+0x22/0x40 mm/kasan/shadow.c:47
Code: 00 00 00 e9 90 ec ff ff 55 41 56 53 48 89 d3 89 f5 49 89 fe 48 8b 4c 24 18 48 89 d6 ba 01 00 00 00 e8 72 ec ff ff 84 c0 74 11 <4c> 89 f7 89 ee 48 89 da 5b 41 5e 5d e9 bd 63 4d 08 31 c0 5b 41 5e
RSP: 0018:ffffc900001b74b0 EFLAGS: 00000002
RAX: 0000000000000001 RBX: 0000000000000010 RCX: ffffffff8139246a
RDX: 0000000000000001 RSI: 0000000000000010 RDI: ffffc900001b75f8
RBP: 0000000000000000 R08: ffffc900001b7607 R09: 1ffff92000036ec0
R10: dffffc0000000000 R11: fffff52000036ec1 R12: 1ffff92000036eb6
R13: dffffc0000000000 R14: ffffc900001b75f8 R15: ffffc900001b75dd
FS: 0000000000000000(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000561da4fa6950 CR3: 000000000c88e000 CR4: 00000000003506e0
Call Trace:
<TASK>
unwind_next_frame+0xb8a/0x20b0 arch/x86/kernel/unwind_orc.c:546
arch_stack_walk+0x10c/0x140 arch/x86/kernel/stacktrace.c:25
stack_trace_save+0xa6/0xf0 kernel/stacktrace.c:122
kasan_save_stack+0x3a/0x60 mm/kasan/common.c:46
__kasan_record_aux_stack+0xb2/0xc0 mm/kasan/generic.c:486
insert_work+0x54/0x3c0 kernel/workqueue.c:1361
__queue_work+0xba3/0xfb0 kernel/workqueue.c:1520
call_timer_fn+0x1ac/0x670 kernel/time/timer.c:1701
expire_timers kernel/time/timer.c:1747 [inline]
__run_timers+0x569/0x800 kernel/time/timer.c:2023
run_timer_softirq+0x63/0xf0 kernel/time/timer.c:2036
handle_softirqs+0x2a1/0x930 kernel/softirq.c:596
run_ksoftirqd+0xa4/0x100 kernel/softirq.c:968
smpboot_thread_fn+0x64a/0xa40 kernel/smpboot.c:164
kthread+0x29d/0x330 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
</TASK>
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup
syzbot found the following issue on:
HEAD commit: 8ce36b2849ef Linux 6.1.163
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=17fe415a580000
kernel config: https://syzkaller.appspot.com/x/.config?x=f0605c5af04d7603
dashboard link: https://syzkaller.appspot.com/bug?extid=ae150307c18be27c9a06
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/25d3bb1313db/disk-8ce36b28.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/53d3c77e16da/vmlinux-8ce36b28.xz
kernel image: https://storage.googleapis.com/syzbot-assets/ca171a78e481/bzImage-8ce36b28.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+ae1503...@syzkaller.appspotmail.com
INFO: task kworker/0:1H:52 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:1H state:D stack:25872 pid:52 ppid:2 flags:0x00004000
Workqueue: glock_workqueue glock_work_func
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5245 [inline]
__schedule+0x11d1/0x40e0 kernel/sched/core.c:6562
schedule+0xb9/0x180 kernel/sched/core.c:6638
io_schedule+0x7c/0xd0 kernel/sched/core.c:8798
bit_wait_io+0xd/0xc0 kernel/sched/wait_bit.c:209
__wait_on_bit_lock+0xd8/0x580 kernel/sched/wait_bit.c:90
out_of_line_wait_on_bit_lock+0x138/0x190 kernel/sched/wait_bit.c:117
wait_on_bit_lock_io include/linux/wait_bit.h:208 [inline]
__lock_buffer fs/buffer.c:69 [inline]
lock_buffer include/linux/buffer_head.h:397 [inline]
discard_buffer fs/buffer.c:1458 [inline]
block_invalidate_folio+0x37b/0x9e0 fs/buffer.c:1515
folio_invalidate mm/truncate.c:158 [inline]
truncate_cleanup_folio+0x218/0x5e0 mm/truncate.c:178
truncate_inode_pages_range+0x293/0x1090 mm/truncate.c:393
do_xmote+0x50a/0x13c0 fs/gfs2/glock.c:801
glock_work_func+0x25e/0x470 fs/gfs2/glock.c:1089
process_one_work+0x8a2/0x1160 kernel/workqueue.c:2292
worker_thread+0xaa2/0x1270 kernel/workqueue.c:2439
kthread+0x29d/0x330 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
</TASK>
INFO: task syz-executor:16118 blocked for more than 144 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor state:D stack:20656 pid:16118 ppid:1 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5245 [inline]
__schedule+0x11d1/0x40e0 kernel/sched/core.c:6562
schedule+0xb9/0x180 kernel/sched/core.c:6638
schedule_timeout+0xbd/0x2d0 kernel/time/timer.c:2144
do_wait_for_common kernel/sched/completion.c:85 [inline]
__wait_for_common kernel/sched/completion.c:106 [inline]
wait_for_common kernel/sched/completion.c:117 [inline]
wait_for_completion+0x2c7/0x5a0 kernel/sched/completion.c:138
__flush_work+0x952/0xae0 kernel/workqueue.c:3076
flush_work kernel/workqueue.c:3097 [inline]
flush_delayed_work+0x12d/0x180 kernel/workqueue.c:3221
gfs2_clear_rgrpd+0xd3/0x6d0 fs/gfs2/rgrp.c:731
gfs2_put_super+0x844/0x8c0 fs/gfs2/super.c:638
generic_shutdown_super+0x130/0x340 fs/super.c:501
kill_block_super+0x7c/0xe0 fs/super.c:1470
deactivate_locked_super+0x93/0xf0 fs/super.c:332
cleanup_mnt+0x42c/0x4b0 fs/namespace.c:1191
task_work_run+0x1d0/0x260 kernel/task_work.c:203
resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
exit_to_user_mode_loop+0xe6/0x110 kernel/entry/common.c:177
exit_to_user_mode_prepare+0xee/0x180 kernel/entry/common.c:210
__syscall_exit_to_user_mode_work kernel/entry/common.c:292 [inline]
syscall_exit_to_user_mode+0x16/0x40 kernel/entry/common.c:303
do_syscall_64+0x58/0xa0 arch/x86/entry/common.c:82
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7ff6d139d1d7
RSP: 002b:00007fff1c87f848 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 00007ff6d1431c3b RCX: 00007ff6d139d1d7
RDX: 0000000000000000 RSI: 0000000000000009 RDI: 00007fff1c87f900
RBP: 00007fff1c87f900 R08: 00007fff1c880900 R09: 00000000ffffffff
R10: 0000000000000000 R11: 0000000000000246 R12: 00007fff1c880990
R13: 00007ff6d1431c3b R14: 000000000019d0d1 R15: 00007fff1c8809d0
</TASK>
Showing all locks held in the system:
1 lock held by rcu_tasks_kthre/12:
#0: ffffffff8cb2dfb0 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x33/0xf00 kernel/rcu/tasks.h:517
1 lock held by rcu_tasks_trace/13:
#0: ffffffff8cb2e7d0 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x33/0xf00 kernel/rcu/tasks.h:517
1 lock held by khungtaskd/28:
#0: ffffffff8cb2d620 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:350 [inline]
#0: ffffffff8cb2d620 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:791 [inline]
#0: ffffffff8cb2d620 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x51/0x290 kernel/locking/lockdep.c:6513
2 locks held by kworker/0:1H/52:
#0: ffff888140f58538 ((wq_completion)glock_workqueue){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
#1: ffffc90000bd7d00 ((work_completion)(&(&gl->gl_work)->work)){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
2 locks held by getty/4026:
#0: ffff88814d5e4098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:244
#1: ffffc9000327b2f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x429/0x1390 drivers/tty/n_tty.c:2198
4 locks held by kworker/u4:7/4372:
#0: ffff888017616938 ((wq_completion)netns){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
#1: ffffc9000468fd00 (net_cleanup_work){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
#2: ffffffff8dd39450 (pernet_ops_rwsem){++++}-{3:3}, at: cleanup_net+0x148/0xba0 net/core/net_namespace.c:594
#3: ffffffff8dd46328 (rtnl_mutex){+.+.}-{3:3}, at: ieee80211_unregister_hw+0x51/0x290 net/mac80211/main.c:1476
3 locks held by kworker/u4:23/6238:
#0: ffff888017479138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
#1: ffffc9000360fd00 ((linkwatch_work).work){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
#2: ffffffff8dd46328 (rtnl_mutex){+.+.}-{3:3}, at: linkwatch_event+0xa/0x50 net/core/link_watch.c:263
2 locks held by kworker/1:14/9481:
#0: ffff888017472138 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
#1: ffffc9000c917d00 ((work_completion)(&rew->rew_work)){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
2 locks held by kworker/1:0/14470:
#0: ffff888017470938 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
#1: ffffc90005fc7d00 (free_ipc_work){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
1 lock held by syz-executor/16118:
#0: ffff888066b1c0e0 (&type->s_umount_key#92){+.+.}-{3:3}, at: deactivate_super+0xa0/0xd0 fs/super.c:362
3 locks held by kworker/0:5/17414:
#0: ffff88814d135d38 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
#1: ffffc90003397d00 ((work_completion)(&(&ifa->dad_work)->work)){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
#2: ffffffff8dd46328 (rtnl_mutex){+.+.}-{3:3}, at: addrconf_dad_work+0xca/0x14f0 net/ipv6/addrconf.c:4131
3 locks held by syz-executor/17810:
#0: ffff88801fbf10b8 (&hdev->req_lock){+.+.}-{3:3}, at: hci_dev_do_close net/bluetooth/hci_core.c:508 [inline]
#0: ffff88801fbf10b8 (&hdev->req_lock){+.+.}-{3:3}, at: hci_unregister_dev+0x1fa/0x4f0 net/bluetooth/hci_core.c:2705
#1: ffff88801fbf0078 (&hdev->lock){+.+.}-{3:3}, at: hci_dev_close_sync+0x458/0xf40 net/bluetooth/hci_sync.c:5233
#2: ffffffff8dea42e8 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_disconn_cfm include/net/bluetooth/hci_core.h:1826 [inline]
#2: ffffffff8dea42e8 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_conn_hash_flush+0xac/0x290 net/bluetooth/hci_conn.c:2504
3 locks held by syz.9.3319/18367:
#0: ffff8880617e10b8 (&hdev->req_lock){+.+.}-{3:3}, at: hci_dev_do_close net/bluetooth/hci_core.c:508 [inline]
#0: ffff8880617e10b8 (&hdev->req_lock){+.+.}-{3:3}, at: hci_unregister_dev+0x1fa/0x4f0 net/bluetooth/hci_core.c:2705
#1: ffff8880617e0078 (&hdev->lock){+.+.}-{3:3}, at: hci_dev_close_sync+0x458/0xf40 net/bluetooth/hci_sync.c:5233
#2: ffffffff8dea42e8 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_disconn_cfm include/net/bluetooth/hci_core.h:1826 [inline]
#2: ffffffff8dea42e8 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_conn_hash_flush+0xac/0x290 net/bluetooth/hci_conn.c:2504
2 locks held by syz.2.3352/18534:
#0: ffffffff8dd46328 (rtnl_mutex){+.+.}-{3:3}, at: tun_detach drivers/net/tun.c:698 [inline]
#0: ffffffff8dd46328 (rtnl_mutex){+.+.}-{3:3}, at: tun_chr_close+0x3d/0x1b0 drivers/net/tun.c:3492
#1: ffffffff8cb332f8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:323 [inline]
#1: ffffffff8cb332f8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x3c0/0x890 kernel/rcu/tree_exp.h:962
3 locks held by syz-executor/18793:
#0: ffff888063a9d0b8 (&hdev->req_lock){+.+.}-{3:3}, at: hci_dev_do_close net/bluetooth/hci_core.c:508 [inline]
#0: ffff888063a9d0b8 (&hdev->req_lock){+.+.}-{3:3}, at: hci_unregister_dev+0x1fa/0x4f0 net/bluetooth/hci_core.c:2705
#1: ffff888063a9c078 (&hdev->lock){+.+.}-{3:3}, at: hci_dev_close_sync+0x458/0xf40 net/bluetooth/hci_sync.c:5233
#2: ffffffff8dea42e8 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_disconn_cfm include/net/bluetooth/hci_core.h:1826 [inline]
#2: ffffffff8dea42e8 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_conn_hash_flush+0xac/0x290 net/bluetooth/hci_conn.c:2504
3 locks held by syz.8.3470/19120:
#0: ffff8880399ad0b8 (&hdev->req_lock){+.+.}-{3:3}, at: hci_dev_do_close net/bluetooth/hci_core.c:508 [inline]
#0: ffff8880399ad0b8 (&hdev->req_lock){+.+.}-{3:3}, at: hci_unregister_dev+0x1fa/0x4f0 net/bluetooth/hci_core.c:2705
#1: ffff8880399ac078 (&hdev->lock){+.+.}-{3:3}, at: hci_dev_close_sync+0x458/0xf40 net/bluetooth/hci_sync.c:5233
#2: ffffffff8cb332f8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:323 [inline]
#2: ffffffff8cb332f8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x3c0/0x890 kernel/rcu/tree_exp.h:962
=============================================
NMI backtrace for cpu 0
CPU: 0 PID: 28 Comm: khungtaskd Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/24/2026
Call Trace:
<TASK>
dump_stack_lvl+0x188/0x24e lib/dump_stack.c:106
nmi_cpu_backtrace+0x3e6/0x460 lib/nmi_backtrace.c:111
nmi_trigger_cpumask_backtrace+0x1d4/0x450 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:220 [inline]
watchdog+0xeee/0xf30 kernel/hung_task.c:377
kthread+0x29d/0x330 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
</TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 21 Comm: ksoftirqd/1 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/24/2026
RIP: 0010:memset+0x22/0x40 mm/kasan/shadow.c:47
Code: 00 00 00 e9 90 ec ff ff 55 41 56 53 48 89 d3 89 f5 49 89 fe 48 8b 4c 24 18 48 89 d6 ba 01 00 00 00 e8 72 ec ff ff 84 c0 74 11 <4c> 89 f7 89 ee 48 89 da 5b 41 5e 5d e9 bd 63 4d 08 31 c0 5b 41 5e
RSP: 0018:ffffc900001b74b0 EFLAGS: 00000002
RAX: 0000000000000001 RBX: 0000000000000010 RCX: ffffffff8139246a
RDX: 0000000000000001 RSI: 0000000000000010 RDI: ffffc900001b75f8
RBP: 0000000000000000 R08: ffffc900001b7607 R09: 1ffff92000036ec0
R10: dffffc0000000000 R11: fffff52000036ec1 R12: 1ffff92000036eb6
R13: dffffc0000000000 R14: ffffc900001b75f8 R15: ffffc900001b75dd
FS: 0000000000000000(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000561da4fa6950 CR3: 000000000c88e000 CR4: 00000000003506e0
Call Trace:
<TASK>
unwind_next_frame+0xb8a/0x20b0 arch/x86/kernel/unwind_orc.c:546
arch_stack_walk+0x10c/0x140 arch/x86/kernel/stacktrace.c:25
stack_trace_save+0xa6/0xf0 kernel/stacktrace.c:122
kasan_save_stack+0x3a/0x60 mm/kasan/common.c:46
__kasan_record_aux_stack+0xb2/0xc0 mm/kasan/generic.c:486
insert_work+0x54/0x3c0 kernel/workqueue.c:1361
__queue_work+0xba3/0xfb0 kernel/workqueue.c:1520
call_timer_fn+0x1ac/0x670 kernel/time/timer.c:1701
expire_timers kernel/time/timer.c:1747 [inline]
__run_timers+0x569/0x800 kernel/time/timer.c:2023
run_timer_softirq+0x63/0xf0 kernel/time/timer.c:2036
handle_softirqs+0x2a1/0x930 kernel/softirq.c:596
run_ksoftirqd+0xa4/0x100 kernel/softirq.c:968
smpboot_thread_fn+0x64a/0xa40 kernel/smpboot.c:164
kthread+0x29d/0x330 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
</TASK>
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup
Reply all
Reply to author
Forward
0 new messages