[v6.6] INFO: task hung in flush_delayed_work
0 views
Skip to first unread message
syzbot
Jul 5, 2026, 1:03:37 PM (10 days ago) Jul 5
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: da47cbc25466 Linux 6.6.144
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=17294b39580000
kernel config: https://syzkaller.appspot.com/x/.config?x=938110aa66424b94
dashboard link: https://syzkaller.appspot.com/bug?extid=ca8f1372ec534fc9d0f3
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/a9e82134d7e6/disk-da47cbc2.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/296a86743157/vmlinux-da47cbc2.xz
kernel image: https://storage.googleapis.com/syzbot-assets/c5adb532f254/bzImage-da47cbc2.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+ca8f13...@syzkaller.appspotmail.com
INFO: task syz-executor:5770 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:21672 pid:5770 ppid:1 flags:0x00004006
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5381 [inline]
__schedule+0x15ae/0x4660 kernel/sched/core.c:6700
schedule+0xbd/0x170 kernel/sched/core.c:6774
schedule_timeout+0xc1/0x2d0 kernel/time/timer.c:2144
do_wait_for_common kernel/sched/completion.c:95 [inline]
__wait_for_common kernel/sched/completion.c:116 [inline]
wait_for_common kernel/sched/completion.c:127 [inline]
wait_for_completion+0x2c6/0x5a0 kernel/sched/completion.c:148
__flush_work+0x92f/0xac0 kernel/workqueue.c:3471
flush_work kernel/workqueue.c:3492 [inline]
flush_delayed_work+0x131/0x180 kernel/workqueue.c:3616
gfs2_clear_rgrpd+0xd7/0x680 fs/gfs2/rgrp.c:731
gfs2_put_super+0x8ab/0x930 fs/gfs2/super.c:647
generic_shutdown_super+0x134/0x2b0 fs/super.c:693
kill_block_super+0x44/0x90 fs/super.c:1660
deactivate_locked_super+0x97/0x100 fs/super.c:481
cleanup_mnt+0x3d7/0x460 fs/namespace.c:1259
task_work_run+0x1d4/0x260 kernel/task_work.c:245
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:291 [inline]
syscall_exit_to_user_mode+0x1a/0x50 kernel/entry/common.c:302
do_syscall_64+0x61/0xb0 arch/x86/entry/common.c:82
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fdc6759f097
RSP: 002b:00007fffafe66b58 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 00007fdc676332ca RCX: 00007fdc6759f097
RDX: 0000000000000000 RSI: 0000000000000009 RDI: 00007fffafe66c10
RBP: 00007fffafe66c10 R08: 00007fffafe67c10 R09: 00000000ffffffff
R10: 0000000000000000 R11: 0000000000000246 R12: 00007fffafe67ca0
R13: 00007fdc676332ca R14: 000000000001ced4 R15: 00007fffafe67ce0
</TASK>
INFO: task kworker/1:2H:5903 blocked for more than 144 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/1:2H state:D stack:26384 pid:5903 ppid:2 flags:0x00004000
Workqueue: glock_workqueue glock_work_func
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5381 [inline]
__schedule+0x15ae/0x4660 kernel/sched/core.c:6700
schedule+0xbd/0x170 kernel/sched/core.c:6774
io_schedule+0x80/0xd0 kernel/sched/core.c:9023
bit_wait_io+0x11/0xd0 kernel/sched/wait_bit.c:209
__wait_on_bit_lock+0xc2/0x560 kernel/sched/wait_bit.c:90
out_of_line_wait_on_bit_lock+0x13c/0x190 kernel/sched/wait_bit.c:117
wait_on_bit_lock_io include/linux/wait_bit.h:208 [inline]
__lock_buffer fs/buffer.c:71 [inline]
lock_buffer include/linux/buffer_head.h:385 [inline]
discard_buffer fs/buffer.c:1564 [inline]
block_invalidate_folio+0x3cb/0xa40 fs/buffer.c:1621
folio_invalidate mm/truncate.c:158 [inline]
truncate_cleanup_folio+0x21f/0x5e0 mm/truncate.c:178
truncate_inode_pages_range+0x275/0xea0 mm/truncate.c:392
do_xmote+0x672/0x11f0 fs/gfs2/glock.c:764
glock_work_func+0x29c/0x4b0 fs/gfs2/glock.c:1119
process_one_work kernel/workqueue.c:2653 [inline]
process_scheduled_works+0xa60/0x1600 kernel/workqueue.c:2730
worker_thread+0xa5e/0xfe0 kernel/workqueue.c:2811
kthread+0x2fa/0x390 kernel/kthread.c:388
ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:152
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:293
</TASK>
Showing all locks held in the system:
2 locks held by kworker/u4:1/13:
#0: ffff888017c71538 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2628 [inline]
#0: ffff888017c71538 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_scheduled_works+0x975/0x1600 kernel/workqueue.c:2730
#1: ffffc90000127d00 (connector_reaper_work){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2628 [inline]
#1: ffffc90000127d00 (connector_reaper_work){+.+.}-{0:0}, at: process_scheduled_works+0x975/0x1600 kernel/workqueue.c:2730
1 lock held by rcu_tasks_kthre/14:
#0: ffffffff8d132750 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0xb11/0xdf0 kernel/rcu/tasks.h:607
1 lock held by khungtaskd/28:
#0: ffffffff8d131da0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:334 [inline]
#0: ffffffff8d131da0 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:786 [inline]
#0: ffffffff8d131da0 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x55/0x290 kernel/locking/lockdep.c:6633
2 locks held by kworker/u4:3/49:
#0: ffff8880b8e3c298 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested+0x9c/0x130 kernel/sched/core.c:567
#1: ffffffff975959a0 (&obj_hash[i].lock){-.-.}-{2:2}, at: process_one_work kernel/workqueue.c:2628 [inline]
#1: ffffffff975959a0 (&obj_hash[i].lock){-.-.}-{2:2}, at: process_scheduled_works+0x975/0x1600 kernel/workqueue.c:2730
2 locks held by getty/5524:
#0: ffff88814c4710a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:243
#1: ffffc9000327b2f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x428/0x1370 drivers/tty/n_tty.c:2217
1 lock held by syz-executor/5770:
#0: ffff8880296580e0 (&type->s_umount_key#63){+.+.}-{3:3}, at: __super_lock fs/super.c:56 [inline]
#0: ffff8880296580e0 (&type->s_umount_key#63){+.+.}-{3:3}, at: __super_lock_excl fs/super.c:71 [inline]
#0: ffff8880296580e0 (&type->s_umount_key#63){+.+.}-{3:3}, at: deactivate_super+0xa4/0xe0 fs/super.c:513
2 locks held by kworker/1:2H/5903:
#0: ffff888142abcd38 ((wq_completion)glock_workqueue){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2628 [inline]
#0: ffff888142abcd38 ((wq_completion)glock_workqueue){+.+.}-{0:0}, at: process_scheduled_works+0x975/0x1600 kernel/workqueue.c:2730
#1: ffffc90003247d00 ((work_completion)(&(&gl->gl_work)->work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2628 [inline]
#1: ffffc90003247d00 ((work_completion)(&(&gl->gl_work)->work)){+.+.}-{0:0}, at: process_scheduled_works+0x975/0x1600 kernel/workqueue.c:2730
1 lock held by syz.0.330/7134:
#0: ffff888032291e20 (&mm->mmap_lock){++++}-{3:3}, at: mmap_write_lock_killable include/linux/mmap_lock.h:124 [inline]
#0: ffff888032291e20 (&mm->mmap_lock){++++}-{3:3}, at: vm_mmap_pgoff+0x166/0x3f0 mm/util.c:554
1 lock held by syz.0.330/7135:
=============================================
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 05/09/2026
Call Trace:
<TASK>
dump_stack_lvl+0x18c/0x250 lib/dump_stack.c:106
nmi_cpu_backtrace+0x3a6/0x3e0 lib/nmi_backtrace.c:113
nmi_trigger_cpumask_backtrace+0x17a/0x2f0 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:160 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:222 [inline]
watchdog+0xf59/0xfa0 kernel/hung_task.c:379
kthread+0x2fa/0x390 kernel/kthread.c:388
ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:152
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:293
</TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 0 Comm: swapper/1 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/09/2026
RIP: 0010:pv_native_safe_halt+0xf/0x10 arch/x86/kernel/paravirt.c:148
Code: 4c 1d 02 c3 cc cc cc cc cc cc cc f3 0f 1e fa 0f 0b 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 66 90 0f 00 2d 43 77 3c 00 fb f4 <c3> 66 0f 1f 00 55 41 57 41 56 41 54 53 50 8b 2f eb 2c 89 cb 80 f9
RSP: 0018:ffffc90000187de0 EFLAGS: 000002c6
RAX: 83e220a6ed73fa00 RBX: ffffffff81628c14 RCX: 83e220a6ed73fa00
RDX: 0000000000000001 RSI: ffffffff8acacb60 RDI: ffffffff8b1cfa20
RBP: ffffc90000187f20 R08: ffff8880b8f36bab R09: 1ffff110171e6d75
R10: dffffc0000000000 R11: ffffed10171e6d76 R12: 1ffff92000030fc8
R13: dffffc0000000000 R14: 1ffff110036cd780 R15: 0000000000000000
FS: 0000000000000000(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f57fc3eb158 CR3: 0000000031747000 CR4: 00000000003506e0
Call Trace:
<TASK>
arch_safe_halt arch/x86/include/asm/paravirt.h:108 [inline]
default_idle+0x13/0x20 arch/x86/kernel/process.c:753
default_idle_call+0x6c/0xa0 kernel/sched/idle.c:97
cpuidle_idle_call kernel/sched/idle.c:178 [inline]
do_idle+0x334/0x5c0 kernel/sched/idle.c:302
cpu_startup_entry+0x43/0x60 kernel/sched/idle.c:401
start_secondary+0xee/0xf0 arch/x86/kernel/smpboot.c:323
secondary_startup_64_no_verify+0x179/0x17b
</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: da47cbc25466 Linux 6.6.144
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=17294b39580000
kernel config: https://syzkaller.appspot.com/x/.config?x=938110aa66424b94
dashboard link: https://syzkaller.appspot.com/bug?extid=ca8f1372ec534fc9d0f3
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/a9e82134d7e6/disk-da47cbc2.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/296a86743157/vmlinux-da47cbc2.xz
kernel image: https://storage.googleapis.com/syzbot-assets/c5adb532f254/bzImage-da47cbc2.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+ca8f13...@syzkaller.appspotmail.com
INFO: task syz-executor:5770 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:21672 pid:5770 ppid:1 flags:0x00004006
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5381 [inline]
__schedule+0x15ae/0x4660 kernel/sched/core.c:6700
schedule+0xbd/0x170 kernel/sched/core.c:6774
schedule_timeout+0xc1/0x2d0 kernel/time/timer.c:2144
do_wait_for_common kernel/sched/completion.c:95 [inline]
__wait_for_common kernel/sched/completion.c:116 [inline]
wait_for_common kernel/sched/completion.c:127 [inline]
wait_for_completion+0x2c6/0x5a0 kernel/sched/completion.c:148
__flush_work+0x92f/0xac0 kernel/workqueue.c:3471
flush_work kernel/workqueue.c:3492 [inline]
flush_delayed_work+0x131/0x180 kernel/workqueue.c:3616
gfs2_clear_rgrpd+0xd7/0x680 fs/gfs2/rgrp.c:731
gfs2_put_super+0x8ab/0x930 fs/gfs2/super.c:647
generic_shutdown_super+0x134/0x2b0 fs/super.c:693
kill_block_super+0x44/0x90 fs/super.c:1660
deactivate_locked_super+0x97/0x100 fs/super.c:481
cleanup_mnt+0x3d7/0x460 fs/namespace.c:1259
task_work_run+0x1d4/0x260 kernel/task_work.c:245
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:291 [inline]
syscall_exit_to_user_mode+0x1a/0x50 kernel/entry/common.c:302
do_syscall_64+0x61/0xb0 arch/x86/entry/common.c:82
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fdc6759f097
RSP: 002b:00007fffafe66b58 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 00007fdc676332ca RCX: 00007fdc6759f097
RDX: 0000000000000000 RSI: 0000000000000009 RDI: 00007fffafe66c10
RBP: 00007fffafe66c10 R08: 00007fffafe67c10 R09: 00000000ffffffff
R10: 0000000000000000 R11: 0000000000000246 R12: 00007fffafe67ca0
R13: 00007fdc676332ca R14: 000000000001ced4 R15: 00007fffafe67ce0
</TASK>
INFO: task kworker/1:2H:5903 blocked for more than 144 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/1:2H state:D stack:26384 pid:5903 ppid:2 flags:0x00004000
Workqueue: glock_workqueue glock_work_func
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5381 [inline]
__schedule+0x15ae/0x4660 kernel/sched/core.c:6700
schedule+0xbd/0x170 kernel/sched/core.c:6774
io_schedule+0x80/0xd0 kernel/sched/core.c:9023
bit_wait_io+0x11/0xd0 kernel/sched/wait_bit.c:209
__wait_on_bit_lock+0xc2/0x560 kernel/sched/wait_bit.c:90
out_of_line_wait_on_bit_lock+0x13c/0x190 kernel/sched/wait_bit.c:117
wait_on_bit_lock_io include/linux/wait_bit.h:208 [inline]
__lock_buffer fs/buffer.c:71 [inline]
lock_buffer include/linux/buffer_head.h:385 [inline]
discard_buffer fs/buffer.c:1564 [inline]
block_invalidate_folio+0x3cb/0xa40 fs/buffer.c:1621
folio_invalidate mm/truncate.c:158 [inline]
truncate_cleanup_folio+0x21f/0x5e0 mm/truncate.c:178
truncate_inode_pages_range+0x275/0xea0 mm/truncate.c:392
do_xmote+0x672/0x11f0 fs/gfs2/glock.c:764
glock_work_func+0x29c/0x4b0 fs/gfs2/glock.c:1119
process_one_work kernel/workqueue.c:2653 [inline]
process_scheduled_works+0xa60/0x1600 kernel/workqueue.c:2730
worker_thread+0xa5e/0xfe0 kernel/workqueue.c:2811
kthread+0x2fa/0x390 kernel/kthread.c:388
ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:152
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:293
</TASK>
Showing all locks held in the system:
2 locks held by kworker/u4:1/13:
#0: ffff888017c71538 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2628 [inline]
#0: ffff888017c71538 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_scheduled_works+0x975/0x1600 kernel/workqueue.c:2730
#1: ffffc90000127d00 (connector_reaper_work){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2628 [inline]
#1: ffffc90000127d00 (connector_reaper_work){+.+.}-{0:0}, at: process_scheduled_works+0x975/0x1600 kernel/workqueue.c:2730
1 lock held by rcu_tasks_kthre/14:
#0: ffffffff8d132750 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0xb11/0xdf0 kernel/rcu/tasks.h:607
1 lock held by khungtaskd/28:
#0: ffffffff8d131da0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:334 [inline]
#0: ffffffff8d131da0 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:786 [inline]
#0: ffffffff8d131da0 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x55/0x290 kernel/locking/lockdep.c:6633
2 locks held by kworker/u4:3/49:
#0: ffff8880b8e3c298 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested+0x9c/0x130 kernel/sched/core.c:567
#1: ffffffff975959a0 (&obj_hash[i].lock){-.-.}-{2:2}, at: process_one_work kernel/workqueue.c:2628 [inline]
#1: ffffffff975959a0 (&obj_hash[i].lock){-.-.}-{2:2}, at: process_scheduled_works+0x975/0x1600 kernel/workqueue.c:2730
2 locks held by getty/5524:
#0: ffff88814c4710a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:243
#1: ffffc9000327b2f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x428/0x1370 drivers/tty/n_tty.c:2217
1 lock held by syz-executor/5770:
#0: ffff8880296580e0 (&type->s_umount_key#63){+.+.}-{3:3}, at: __super_lock fs/super.c:56 [inline]
#0: ffff8880296580e0 (&type->s_umount_key#63){+.+.}-{3:3}, at: __super_lock_excl fs/super.c:71 [inline]
#0: ffff8880296580e0 (&type->s_umount_key#63){+.+.}-{3:3}, at: deactivate_super+0xa4/0xe0 fs/super.c:513
2 locks held by kworker/1:2H/5903:
#0: ffff888142abcd38 ((wq_completion)glock_workqueue){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2628 [inline]
#0: ffff888142abcd38 ((wq_completion)glock_workqueue){+.+.}-{0:0}, at: process_scheduled_works+0x975/0x1600 kernel/workqueue.c:2730
#1: ffffc90003247d00 ((work_completion)(&(&gl->gl_work)->work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2628 [inline]
#1: ffffc90003247d00 ((work_completion)(&(&gl->gl_work)->work)){+.+.}-{0:0}, at: process_scheduled_works+0x975/0x1600 kernel/workqueue.c:2730
1 lock held by syz.0.330/7134:
#0: ffff888032291e20 (&mm->mmap_lock){++++}-{3:3}, at: mmap_write_lock_killable include/linux/mmap_lock.h:124 [inline]
#0: ffff888032291e20 (&mm->mmap_lock){++++}-{3:3}, at: vm_mmap_pgoff+0x166/0x3f0 mm/util.c:554
1 lock held by syz.0.330/7135:
=============================================
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 05/09/2026
Call Trace:
<TASK>
dump_stack_lvl+0x18c/0x250 lib/dump_stack.c:106
nmi_cpu_backtrace+0x3a6/0x3e0 lib/nmi_backtrace.c:113
nmi_trigger_cpumask_backtrace+0x17a/0x2f0 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:160 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:222 [inline]
watchdog+0xf59/0xfa0 kernel/hung_task.c:379
kthread+0x2fa/0x390 kernel/kthread.c:388
ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:152
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:293
</TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 0 Comm: swapper/1 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/09/2026
RIP: 0010:pv_native_safe_halt+0xf/0x10 arch/x86/kernel/paravirt.c:148
Code: 4c 1d 02 c3 cc cc cc cc cc cc cc f3 0f 1e fa 0f 0b 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 66 90 0f 00 2d 43 77 3c 00 fb f4 <c3> 66 0f 1f 00 55 41 57 41 56 41 54 53 50 8b 2f eb 2c 89 cb 80 f9
RSP: 0018:ffffc90000187de0 EFLAGS: 000002c6
RAX: 83e220a6ed73fa00 RBX: ffffffff81628c14 RCX: 83e220a6ed73fa00
RDX: 0000000000000001 RSI: ffffffff8acacb60 RDI: ffffffff8b1cfa20
RBP: ffffc90000187f20 R08: ffff8880b8f36bab R09: 1ffff110171e6d75
R10: dffffc0000000000 R11: ffffed10171e6d76 R12: 1ffff92000030fc8
R13: dffffc0000000000 R14: 1ffff110036cd780 R15: 0000000000000000
FS: 0000000000000000(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f57fc3eb158 CR3: 0000000031747000 CR4: 00000000003506e0
Call Trace:
<TASK>
arch_safe_halt arch/x86/include/asm/paravirt.h:108 [inline]
default_idle+0x13/0x20 arch/x86/kernel/process.c:753
default_idle_call+0x6c/0xa0 kernel/sched/idle.c:97
cpuidle_idle_call kernel/sched/idle.c:178 [inline]
do_idle+0x334/0x5c0 kernel/sched/idle.c:302
cpu_startup_entry+0x43/0x60 kernel/sched/idle.c:401
start_secondary+0xee/0xf0 arch/x86/kernel/smpboot.c:323
secondary_startup_64_no_verify+0x179/0x17b
</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