[v6.6] INFO: task hung in do_coredump
0 views
Skip to first unread message
syzbot
Sep 17, 2025, 2:48:41 AM (3 days ago) Sep 17
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 60a9e718726f Linux 6.6.106
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13dd4534580000
kernel config: https://syzkaller.appspot.com/x/.config?x=12606d4b8832c7e4
dashboard link: https://syzkaller.appspot.com/bug?extid=3ce7863f8fc836a427e7
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/eca27e056a5a/disk-60a9e718.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/bc64d4eeb7f6/vmlinux-60a9e718.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a345041561ac/bzImage-60a9e718.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+3ce786...@syzkaller.appspotmail.com
INFO: task syz.4.881:9206 blocked for more than 143 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.4.881 state:D stack:26280 pid:9206 ppid:6483 flags:0x00004006
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5380 [inline]
__schedule+0x14d2/0x44d0 kernel/sched/core.c:6699
schedule+0xbd/0x170 kernel/sched/core.c:6773
schedule_timeout+0x9b/0x280 kernel/time/timer.c:2143
do_wait_for_common kernel/sched/completion.c:95 [inline]
__wait_for_common+0x3cb/0x6d0 kernel/sched/completion.c:116
wait_for_common kernel/sched/completion.c:127 [inline]
wait_for_completion_state+0x1c/0x40 kernel/sched/completion.c:264
coredump_wait fs/coredump.c:443 [inline]
do_coredump+0x85c/0x2480 fs/coredump.c:640
get_signal+0x1133/0x1400 kernel/signal.c:2888
arch_do_signal_or_restart+0x96/0x780 arch/x86/kernel/signal.c:310
exit_to_user_mode_loop+0x70/0x110 kernel/entry/common.c:174
exit_to_user_mode_prepare+0xf6/0x180 kernel/entry/common.c:210
irqentry_exit_to_user_mode+0x9/0x40 kernel/entry/common.c:315
exc_page_fault+0x8f/0x110 arch/x86/mm/fault.c:1524
asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:608
RIP: 0033:0x7ff7f3a4f927
RSP: 002b:00007ffc46f29060 EFLAGS: 00010206
RAX: 0000000000000000 RBX: 000000000000000b RCX: 000000000007bc78
RDX: 00007ffc46f29080 RSI: 00007ffc46f291b0 RDI: 000000000000000b
RBP: 00007ff7f3dd7da0 R08: 00000000000001fb R09: 0000000000745d1e
R10: 000001063ce6e5f8 R11: 0000000000018346 R12: 000000000007c249
R13: 00007ff7f3dd6090 R14: ffffffffffffffff R15: 00007ffc470272e0
</TASK>
INFO: task syz.4.881:9208 blocked for more than 144 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.4.881 state:D stack:26856 pid:9208 ppid:6483 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5380 [inline]
__schedule+0x14d2/0x44d0 kernel/sched/core.c:6699
schedule+0xbd/0x170 kernel/sched/core.c:6773
coredump_task_exit kernel/exit.c:436 [inline]
do_exit+0x4a0/0x23c0 kernel/exit.c:825
do_group_exit+0x21b/0x2d0 kernel/exit.c:1024
get_signal+0x12fc/0x1400 kernel/signal.c:2902
arch_do_signal_or_restart+0x96/0x780 arch/x86/kernel/signal.c:310
exit_to_user_mode_loop+0x70/0x110 kernel/entry/common.c:174
exit_to_user_mode_prepare+0xf6/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:87
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7ff7f3b8eba9
RSP: 002b:00007ff7f494c0e8 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca
RAX: fffffffffffffe00 RBX: 00007ff7f3dd6098 RCX: 00007ff7f3b8eba9
RDX: 0000000000000000 RSI: 0000000000000080 RDI: 00007ff7f3dd6098
RBP: 00007ff7f3dd6090 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ff7f3dd6128 R14: 00007ffc47026f80 R15: 00007ffc47027068
</TASK>
Showing all locks held in the system:
1 lock held by khungtaskd/29:
#0: ffffffff8cd2fe20 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:334 [inline]
#0: ffffffff8cd2fe20 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:786 [inline]
#0: ffffffff8cd2fe20 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x55/0x290 kernel/locking/lockdep.c:6633
4 locks held by kworker/u4:13/3538:
#0: ffff888017873938 ((wq_completion)netns){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2609 [inline]
#0: ffff888017873938 ((wq_completion)netns){+.+.}-{0:0}, at: process_scheduled_works+0x957/0x15b0 kernel/workqueue.c:2711
#1: ffffc9000cb87d00 (net_cleanup_work){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2609 [inline]
#1: ffffc9000cb87d00 (net_cleanup_work){+.+.}-{0:0}, at: process_scheduled_works+0x957/0x15b0 kernel/workqueue.c:2711
#2: ffffffff8dfafad0 (pernet_ops_rwsem){++++}-{3:3}, at: cleanup_net+0x136/0xb90 net/core/net_namespace.c:606
#3: ffffffff8cd35cc0 (rcu_state.barrier_mutex){+.+.}-{3:3}, at: rcu_barrier+0x4c/0x580 kernel/rcu/tree.c:4089
2 locks held by getty/5558:
#0: ffff88814ce3f0a0 (&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+0x425/0x1380 drivers/tty/n_tty.c:2217
5 locks held by khidpd_15c25886/10225:
#0: ffff8880264f40b8 (&hdev->lock){+.+.}-{3:3}, at: l2cap_unregister_user+0x6a/0x1a0 net/bluetooth/l2cap_core.c:1728
#1: ffffffff8e155af0 (hidp_session_sem){++++}-{3:3}, at: hidp_session_remove+0x2c/0x260 net/bluetooth/hidp/core.c:1165
#2: ffffffff8da78e08 (input_mutex){+.+.}-{3:3}, at: __input_unregister_device+0x2ee/0x5f0 drivers/input/input.c:2293
#3: ffff888024c1e4e0 (&led_cdev->trigger_lock){+.+.}-{3:3}, at: led_classdev_unregister+0x70/0x280 drivers/leds/led-class.c:586
#4: ffffffff8cd35df8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:292 [inline]
#4: ffffffff8cd35df8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x448/0x830 kernel/rcu/tree_exp.h:1004
2 locks held by syz.8.1157/10260:
#0: ffff88804f7a8e20 (&sb->s_type->i_mutex_key#10){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:804 [inline]
#0: ffff88804f7a8e20 (&sb->s_type->i_mutex_key#10){+.+.}-{3:3}, at: __sock_release net/socket.c:658 [inline]
#0: ffff88804f7a8e20 (&sb->s_type->i_mutex_key#10){+.+.}-{3:3}, at: sock_close+0x9b/0x230 net/socket.c:1421
#1: ffffffff8cd35df8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:324 [inline]
#1: ffffffff8cd35df8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x360/0x830 kernel/rcu/tree_exp.h:1004
=============================================
NMI backtrace for cpu 0
CPU: 0 PID: 29 Comm: khungtaskd Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025
Call Trace:
<TASK>
dump_stack_lvl+0x16c/0x230 lib/dump_stack.c:106
nmi_cpu_backtrace+0x39b/0x3d0 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+0xf41/0xf80 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: 1126 Comm: kworker/u4:6 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025
Workqueue: bat_events batadv_iv_send_outstanding_bat_ogm_packet
RIP: 0010:rcu_dynticks_curr_cpu_in_eqs include/linux/context_tracking.h:122 [inline]
RIP: 0010:rcu_is_watching+0x3a/0xb0 kernel/rcu/tree.c:700
Code: e8 2b 96 fe 08 89 c3 83 f8 08 73 60 49 bf 00 00 00 00 00 fc ff df 4c 8d 34 dd 30 3a 7d 8c 4c 89 f0 48 c1 e8 03 42 80 3c 38 00 <74> 08 4c 89 f7 e8 bc 42 6d 00 48 c7 c3 68 6d 03 00 49 03 1e 48 89
RSP: 0018:ffffc9000474f880 EFLAGS: 00000246
RAX: 1ffffffff18fa747 RBX: 0000000000000001 RCX: 1182928c41415500
RDX: 0000000000000000 RSI: ffffffff8afc72a0 RDI: ffffffff8afc7260
RBP: ffffc9000474f9b0 R08: ffffffff8e4a94ef R09: 1ffffffff1c9529d
R10: dffffc0000000000 R11: fffffbfff1c9529e R12: ffffffff8a320aa3
R13: dffffc0000000000 R14: ffffffff8c7d3a38 R15: dffffc0000000000
FS: 0000000000000000(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fdf2d9a4198 CR3: 000000002e317000 CR4: 00000000003506e0
DR0: 0000000000000008 DR1: fffffffffffffffd DR2: 0000000000000003
DR3: 0000000000000004 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
trace_lock_release include/trace/events/lock.h:69 [inline]
lock_release+0xba/0x8b0 kernel/locking/lockdep.c:5765
rcu_lock_release include/linux/rcupdate.h:344 [inline]
rcu_read_unlock include/linux/rcupdate.h:819 [inline]
batadv_iv_ogm_slide_own_bcast_window net/batman-adv/bat_iv_ogm.c:770 [inline]
batadv_iv_ogm_schedule_buff net/batman-adv/bat_iv_ogm.c:824 [inline]
batadv_iv_ogm_schedule+0x6d1/0xe90 net/batman-adv/bat_iv_ogm.c:867
batadv_iv_send_outstanding_bat_ogm_packet+0x731/0x840 net/batman-adv/bat_iv_ogm.c:1711
process_one_work kernel/workqueue.c:2634 [inline]
process_scheduled_works+0xa45/0x15b0 kernel/workqueue.c:2711
worker_thread+0xa55/0xfc0 kernel/workqueue.c:2792
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>
---
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: 60a9e718726f Linux 6.6.106
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13dd4534580000
kernel config: https://syzkaller.appspot.com/x/.config?x=12606d4b8832c7e4
dashboard link: https://syzkaller.appspot.com/bug?extid=3ce7863f8fc836a427e7
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/eca27e056a5a/disk-60a9e718.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/bc64d4eeb7f6/vmlinux-60a9e718.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a345041561ac/bzImage-60a9e718.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+3ce786...@syzkaller.appspotmail.com
INFO: task syz.4.881:9206 blocked for more than 143 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.4.881 state:D stack:26280 pid:9206 ppid:6483 flags:0x00004006
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5380 [inline]
__schedule+0x14d2/0x44d0 kernel/sched/core.c:6699
schedule+0xbd/0x170 kernel/sched/core.c:6773
schedule_timeout+0x9b/0x280 kernel/time/timer.c:2143
do_wait_for_common kernel/sched/completion.c:95 [inline]
__wait_for_common+0x3cb/0x6d0 kernel/sched/completion.c:116
wait_for_common kernel/sched/completion.c:127 [inline]
wait_for_completion_state+0x1c/0x40 kernel/sched/completion.c:264
coredump_wait fs/coredump.c:443 [inline]
do_coredump+0x85c/0x2480 fs/coredump.c:640
get_signal+0x1133/0x1400 kernel/signal.c:2888
arch_do_signal_or_restart+0x96/0x780 arch/x86/kernel/signal.c:310
exit_to_user_mode_loop+0x70/0x110 kernel/entry/common.c:174
exit_to_user_mode_prepare+0xf6/0x180 kernel/entry/common.c:210
irqentry_exit_to_user_mode+0x9/0x40 kernel/entry/common.c:315
exc_page_fault+0x8f/0x110 arch/x86/mm/fault.c:1524
asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:608
RIP: 0033:0x7ff7f3a4f927
RSP: 002b:00007ffc46f29060 EFLAGS: 00010206
RAX: 0000000000000000 RBX: 000000000000000b RCX: 000000000007bc78
RDX: 00007ffc46f29080 RSI: 00007ffc46f291b0 RDI: 000000000000000b
RBP: 00007ff7f3dd7da0 R08: 00000000000001fb R09: 0000000000745d1e
R10: 000001063ce6e5f8 R11: 0000000000018346 R12: 000000000007c249
R13: 00007ff7f3dd6090 R14: ffffffffffffffff R15: 00007ffc470272e0
</TASK>
INFO: task syz.4.881:9208 blocked for more than 144 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.4.881 state:D stack:26856 pid:9208 ppid:6483 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5380 [inline]
__schedule+0x14d2/0x44d0 kernel/sched/core.c:6699
schedule+0xbd/0x170 kernel/sched/core.c:6773
coredump_task_exit kernel/exit.c:436 [inline]
do_exit+0x4a0/0x23c0 kernel/exit.c:825
do_group_exit+0x21b/0x2d0 kernel/exit.c:1024
get_signal+0x12fc/0x1400 kernel/signal.c:2902
arch_do_signal_or_restart+0x96/0x780 arch/x86/kernel/signal.c:310
exit_to_user_mode_loop+0x70/0x110 kernel/entry/common.c:174
exit_to_user_mode_prepare+0xf6/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:87
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7ff7f3b8eba9
RSP: 002b:00007ff7f494c0e8 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca
RAX: fffffffffffffe00 RBX: 00007ff7f3dd6098 RCX: 00007ff7f3b8eba9
RDX: 0000000000000000 RSI: 0000000000000080 RDI: 00007ff7f3dd6098
RBP: 00007ff7f3dd6090 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ff7f3dd6128 R14: 00007ffc47026f80 R15: 00007ffc47027068
</TASK>
Showing all locks held in the system:
1 lock held by khungtaskd/29:
#0: ffffffff8cd2fe20 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:334 [inline]
#0: ffffffff8cd2fe20 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:786 [inline]
#0: ffffffff8cd2fe20 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x55/0x290 kernel/locking/lockdep.c:6633
4 locks held by kworker/u4:13/3538:
#0: ffff888017873938 ((wq_completion)netns){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2609 [inline]
#0: ffff888017873938 ((wq_completion)netns){+.+.}-{0:0}, at: process_scheduled_works+0x957/0x15b0 kernel/workqueue.c:2711
#1: ffffc9000cb87d00 (net_cleanup_work){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2609 [inline]
#1: ffffc9000cb87d00 (net_cleanup_work){+.+.}-{0:0}, at: process_scheduled_works+0x957/0x15b0 kernel/workqueue.c:2711
#2: ffffffff8dfafad0 (pernet_ops_rwsem){++++}-{3:3}, at: cleanup_net+0x136/0xb90 net/core/net_namespace.c:606
#3: ffffffff8cd35cc0 (rcu_state.barrier_mutex){+.+.}-{3:3}, at: rcu_barrier+0x4c/0x580 kernel/rcu/tree.c:4089
2 locks held by getty/5558:
#0: ffff88814ce3f0a0 (&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+0x425/0x1380 drivers/tty/n_tty.c:2217
5 locks held by khidpd_15c25886/10225:
#0: ffff8880264f40b8 (&hdev->lock){+.+.}-{3:3}, at: l2cap_unregister_user+0x6a/0x1a0 net/bluetooth/l2cap_core.c:1728
#1: ffffffff8e155af0 (hidp_session_sem){++++}-{3:3}, at: hidp_session_remove+0x2c/0x260 net/bluetooth/hidp/core.c:1165
#2: ffffffff8da78e08 (input_mutex){+.+.}-{3:3}, at: __input_unregister_device+0x2ee/0x5f0 drivers/input/input.c:2293
#3: ffff888024c1e4e0 (&led_cdev->trigger_lock){+.+.}-{3:3}, at: led_classdev_unregister+0x70/0x280 drivers/leds/led-class.c:586
#4: ffffffff8cd35df8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:292 [inline]
#4: ffffffff8cd35df8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x448/0x830 kernel/rcu/tree_exp.h:1004
2 locks held by syz.8.1157/10260:
#0: ffff88804f7a8e20 (&sb->s_type->i_mutex_key#10){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:804 [inline]
#0: ffff88804f7a8e20 (&sb->s_type->i_mutex_key#10){+.+.}-{3:3}, at: __sock_release net/socket.c:658 [inline]
#0: ffff88804f7a8e20 (&sb->s_type->i_mutex_key#10){+.+.}-{3:3}, at: sock_close+0x9b/0x230 net/socket.c:1421
#1: ffffffff8cd35df8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:324 [inline]
#1: ffffffff8cd35df8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x360/0x830 kernel/rcu/tree_exp.h:1004
=============================================
NMI backtrace for cpu 0
CPU: 0 PID: 29 Comm: khungtaskd Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025
Call Trace:
<TASK>
dump_stack_lvl+0x16c/0x230 lib/dump_stack.c:106
nmi_cpu_backtrace+0x39b/0x3d0 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+0xf41/0xf80 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: 1126 Comm: kworker/u4:6 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025
Workqueue: bat_events batadv_iv_send_outstanding_bat_ogm_packet
RIP: 0010:rcu_dynticks_curr_cpu_in_eqs include/linux/context_tracking.h:122 [inline]
RIP: 0010:rcu_is_watching+0x3a/0xb0 kernel/rcu/tree.c:700
Code: e8 2b 96 fe 08 89 c3 83 f8 08 73 60 49 bf 00 00 00 00 00 fc ff df 4c 8d 34 dd 30 3a 7d 8c 4c 89 f0 48 c1 e8 03 42 80 3c 38 00 <74> 08 4c 89 f7 e8 bc 42 6d 00 48 c7 c3 68 6d 03 00 49 03 1e 48 89
RSP: 0018:ffffc9000474f880 EFLAGS: 00000246
RAX: 1ffffffff18fa747 RBX: 0000000000000001 RCX: 1182928c41415500
RDX: 0000000000000000 RSI: ffffffff8afc72a0 RDI: ffffffff8afc7260
RBP: ffffc9000474f9b0 R08: ffffffff8e4a94ef R09: 1ffffffff1c9529d
R10: dffffc0000000000 R11: fffffbfff1c9529e R12: ffffffff8a320aa3
R13: dffffc0000000000 R14: ffffffff8c7d3a38 R15: dffffc0000000000
FS: 0000000000000000(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fdf2d9a4198 CR3: 000000002e317000 CR4: 00000000003506e0
DR0: 0000000000000008 DR1: fffffffffffffffd DR2: 0000000000000003
DR3: 0000000000000004 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
trace_lock_release include/trace/events/lock.h:69 [inline]
lock_release+0xba/0x8b0 kernel/locking/lockdep.c:5765
rcu_lock_release include/linux/rcupdate.h:344 [inline]
rcu_read_unlock include/linux/rcupdate.h:819 [inline]
batadv_iv_ogm_slide_own_bcast_window net/batman-adv/bat_iv_ogm.c:770 [inline]
batadv_iv_ogm_schedule_buff net/batman-adv/bat_iv_ogm.c:824 [inline]
batadv_iv_ogm_schedule+0x6d1/0xe90 net/batman-adv/bat_iv_ogm.c:867
batadv_iv_send_outstanding_bat_ogm_packet+0x731/0x840 net/batman-adv/bat_iv_ogm.c:1711
process_one_work kernel/workqueue.c:2634 [inline]
process_scheduled_works+0xa45/0x15b0 kernel/workqueue.c:2711
worker_thread+0xa55/0xfc0 kernel/workqueue.c:2792
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>
---
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
Sep 17, 2025, 6:03:30 AM (3 days ago) Sep 17
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:
HEAD commit: 60a9e718726f Linux 6.6.106
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=16210712580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13d5af62580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/eca27e056a5a/disk-60a9e718.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/bc64d4eeb7f6/vmlinux-60a9e718.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a345041561ac/bzImage-60a9e718.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+3ce786...@syzkaller.appspotmail.com
INFO: task syz.0.17:5963 blocked for more than 143 seconds.
RSP: 002b:00007ffc2b27f020 EFLAGS: 00010202
RAX: 0000000000000000 RBX: 000000000000000b RCX: ffffffffffffffa8
RDX: 00007ffc2b27f040 RSI: 00007ffc2b27f170 RDI: 000000000000000b
RBP: 0000000000000032 R08: 0000000000745d1e R09: 000000062b37da2f
R10: 00007ffc2b37d830 R11: 0000000000000246 R12: 00007fea6d5d609c
R13: 00007ffc2b37d830 R14: 000000000002620b R15: 00007ffc2b37d850
</TASK>
INFO: task syz.0.17:5965 blocked for more than 143 seconds.
RSP: 002b:00007fea6e2b60e8 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca
RAX: fffffffffffffe00 RBX: 00007fea6d5d6098 RCX: 00007fea6d38eba9
RDX: 0000000000000000 RSI: 0000000000000080 RDI: 00007fea6d5d6098
RBP: 00007fea6d5d6090 R08: 0000000000000000 R09: 0000000000000000
2 locks held by getty/5548:
#0: ffff88802cc560a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:243
NMI backtrace for cpu 1
CPU: 1 PID: 29 Comm: khungtaskd Not tainted syzkaller #0
RIP: 0010:on_stack arch/x86/include/asm/stacktrace.h:55 [inline]
RIP: 0010:stack_access_ok arch/x86/kernel/unwind_orc.c:393 [inline]
RIP: 0010:deref_stack_reg+0x4c/0x240 arch/x86/kernel/unwind_orc.c:403
Code: ff df e8 47 c1 4a 00 49 8d 5f 08 48 89 d8 48 c1 e8 03 48 89 44 24 10 80 3c 28 00 74 08 48 89 df e8 49 0c a2 00 48 89 5c 24 18 <4d> 8b 77 08 49 8d 5f 10 49 89 dd 49 c1 ed 03 41 80 7c 2d 00 00 74
RSP: 0018:ffffc90002e27478 EFLAGS: 00000246
RAX: 1ffff920005c4eb6 RBX: ffffc90002e275b0 RCX: ffff88801af48000
RDX: 0000000000000000 RSI: ffffc90002e27da8 RDI: ffffc90002e275a8
RBP: dffffc0000000000 R08: ffff88801af48000 R09: 0000000000000003
R10: 0000000000000004 R11: 0000000000000000 R12: ffffc90002e275a8
R13: dffffc0000000000 R14: ffffffff8ece8a94 R15: ffffc90002e275a8
FS: 0000000000000000(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
Call Trace:
<TASK>
unwind_next_frame+0x1789/0x2970 arch/x86/kernel/unwind_orc.c:648
arch_stack_walk+0x144/0x190 arch/x86/kernel/stacktrace.c:25
stack_trace_save+0x9c/0xe0 kernel/stacktrace.c:122
kasan_save_stack mm/kasan/common.c:45 [inline]
kasan_set_track+0x4e/0x70 mm/kasan/common.c:52
kasan_save_free_info+0x2e/0x50 mm/kasan/generic.c:522
____kasan_slab_free+0x126/0x1e0 mm/kasan/common.c:236
kasan_slab_free include/linux/kasan.h:164 [inline]
slab_free_hook mm/slub.c:1811 [inline]
slab_free_freelist_hook+0x130/0x1b0 mm/slub.c:1837
slab_free mm/slub.c:3830 [inline]
__kmem_cache_free+0xba/0x1f0 mm/slub.c:3843
skb_kfree_head net/core/skbuff.c:945 [inline]
skb_free_head net/core/skbuff.c:957 [inline]
skb_release_data+0x634/0x800 net/core/skbuff.c:987
skb_release_all net/core/skbuff.c:1053 [inline]
__kfree_skb net/core/skbuff.c:1067 [inline]
consume_skb+0xb2/0x110 net/core/skbuff.c:1283
nsim_dev_trap_report drivers/net/netdevsim/dev.c:821 [inline]
nsim_dev_trap_report_work+0x76f/0xb00 drivers/net/netdevsim/dev.c:851
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
HEAD commit: 60a9e718726f Linux 6.6.106
git tree: linux-6.6.y
kernel config: https://syzkaller.appspot.com/x/.config?x=12606d4b8832c7e4
dashboard link: https://syzkaller.appspot.com/bug?extid=3ce7863f8fc836a427e7
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=172d1f62580000
dashboard link: https://syzkaller.appspot.com/bug?extid=3ce7863f8fc836a427e7
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13d5af62580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/eca27e056a5a/disk-60a9e718.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/bc64d4eeb7f6/vmlinux-60a9e718.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a345041561ac/bzImage-60a9e718.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+3ce786...@syzkaller.appspotmail.com
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.0.17 state:D stack:25544 pid:5963 ppid:5917 flags:0x00004004
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5380 [inline]
__schedule+0x14d2/0x44d0 kernel/sched/core.c:6699
schedule+0xbd/0x170 kernel/sched/core.c:6773
<TASK>
context_switch kernel/sched/core.c:5380 [inline]
__schedule+0x14d2/0x44d0 kernel/sched/core.c:6699
schedule+0xbd/0x170 kernel/sched/core.c:6773
schedule_timeout+0x9b/0x280 kernel/time/timer.c:2143
do_wait_for_common kernel/sched/completion.c:95 [inline]
__wait_for_common+0x3cb/0x6d0 kernel/sched/completion.c:116
wait_for_common kernel/sched/completion.c:127 [inline]
wait_for_completion_state+0x1c/0x40 kernel/sched/completion.c:264
coredump_wait fs/coredump.c:443 [inline]
do_coredump+0x85c/0x2480 fs/coredump.c:640
get_signal+0x1133/0x1400 kernel/signal.c:2888
arch_do_signal_or_restart+0x96/0x780 arch/x86/kernel/signal.c:310
exit_to_user_mode_loop+0x70/0x110 kernel/entry/common.c:174
exit_to_user_mode_prepare+0xf6/0x180 kernel/entry/common.c:210
irqentry_exit_to_user_mode+0x9/0x40 kernel/entry/common.c:315
exc_page_fault+0x8f/0x110 arch/x86/mm/fault.c:1524
asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:608
RIP: 0033:0x7fea6d24f927
do_wait_for_common kernel/sched/completion.c:95 [inline]
__wait_for_common+0x3cb/0x6d0 kernel/sched/completion.c:116
wait_for_common kernel/sched/completion.c:127 [inline]
wait_for_completion_state+0x1c/0x40 kernel/sched/completion.c:264
coredump_wait fs/coredump.c:443 [inline]
do_coredump+0x85c/0x2480 fs/coredump.c:640
get_signal+0x1133/0x1400 kernel/signal.c:2888
arch_do_signal_or_restart+0x96/0x780 arch/x86/kernel/signal.c:310
exit_to_user_mode_loop+0x70/0x110 kernel/entry/common.c:174
exit_to_user_mode_prepare+0xf6/0x180 kernel/entry/common.c:210
irqentry_exit_to_user_mode+0x9/0x40 kernel/entry/common.c:315
exc_page_fault+0x8f/0x110 arch/x86/mm/fault.c:1524
asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:608
RSP: 002b:00007ffc2b27f020 EFLAGS: 00010202
RAX: 0000000000000000 RBX: 000000000000000b RCX: ffffffffffffffa8
RDX: 00007ffc2b27f040 RSI: 00007ffc2b27f170 RDI: 000000000000000b
RBP: 0000000000000032 R08: 0000000000745d1e R09: 000000062b37da2f
R10: 00007ffc2b37d830 R11: 0000000000000246 R12: 00007fea6d5d609c
R13: 00007ffc2b37d830 R14: 000000000002620b R15: 00007ffc2b37d850
</TASK>
INFO: task syz.0.17:5965 blocked for more than 143 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.0.17 state:D stack:26696 pid:5965 ppid:5917 flags:0x00004004
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5380 [inline]
__schedule+0x14d2/0x44d0 kernel/sched/core.c:6699
schedule+0xbd/0x170 kernel/sched/core.c:6773
coredump_task_exit kernel/exit.c:436 [inline]
do_exit+0x4a0/0x23c0 kernel/exit.c:825
do_group_exit+0x21b/0x2d0 kernel/exit.c:1024
get_signal+0x12fc/0x1400 kernel/signal.c:2902
arch_do_signal_or_restart+0x96/0x780 arch/x86/kernel/signal.c:310
exit_to_user_mode_loop+0x70/0x110 kernel/entry/common.c:174
exit_to_user_mode_prepare+0xf6/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:87
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fea6d38eba9
<TASK>
context_switch kernel/sched/core.c:5380 [inline]
__schedule+0x14d2/0x44d0 kernel/sched/core.c:6699
schedule+0xbd/0x170 kernel/sched/core.c:6773
coredump_task_exit kernel/exit.c:436 [inline]
do_exit+0x4a0/0x23c0 kernel/exit.c:825
do_group_exit+0x21b/0x2d0 kernel/exit.c:1024
get_signal+0x12fc/0x1400 kernel/signal.c:2902
arch_do_signal_or_restart+0x96/0x780 arch/x86/kernel/signal.c:310
exit_to_user_mode_loop+0x70/0x110 kernel/entry/common.c:174
exit_to_user_mode_prepare+0xf6/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:87
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RSP: 002b:00007fea6e2b60e8 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca
RAX: fffffffffffffe00 RBX: 00007fea6d5d6098 RCX: 00007fea6d38eba9
RDX: 0000000000000000 RSI: 0000000000000080 RDI: 00007fea6d5d6098
RBP: 00007fea6d5d6090 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fea6d5d6128 R14: 00007ffc2b37d4f0 R15: 00007ffc2b37d5d8
</TASK>
Showing all locks held in the system:
1 lock held by khungtaskd/29:
#0: ffffffff8cd2fe20 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:334 [inline]
#0: ffffffff8cd2fe20 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:786 [inline]
#0: ffffffff8cd2fe20 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x55/0x290 kernel/locking/lockdep.c:6633
2 locks held by kworker/u4:5/137:
Showing all locks held in the system:
1 lock held by khungtaskd/29:
#0: ffffffff8cd2fe20 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:334 [inline]
#0: ffffffff8cd2fe20 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:786 [inline]
#0: ffffffff8cd2fe20 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x55/0x290 kernel/locking/lockdep.c:6633
2 locks held by getty/5548:
#0: ffff88802cc560a0 (&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+0x425/0x1380 drivers/tty/n_tty.c:2217
=============================================
NMI backtrace for cpu 1
CPU: 1 PID: 29 Comm: khungtaskd Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025
Call Trace:
<TASK>
dump_stack_lvl+0x16c/0x230 lib/dump_stack.c:106
nmi_cpu_backtrace+0x39b/0x3d0 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+0xf41/0xf80 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 1 to CPUs 0:
Call Trace:
<TASK>
dump_stack_lvl+0x16c/0x230 lib/dump_stack.c:106
nmi_cpu_backtrace+0x39b/0x3d0 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+0xf41/0xf80 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>
NMI backtrace for cpu 0
CPU: 0 PID: 137 Comm: kworker/u4:5 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025
Workqueue: events_unbound nsim_dev_trap_report_work
RIP: 0010:on_stack arch/x86/include/asm/stacktrace.h:55 [inline]
RIP: 0010:stack_access_ok arch/x86/kernel/unwind_orc.c:393 [inline]
RIP: 0010:deref_stack_reg+0x4c/0x240 arch/x86/kernel/unwind_orc.c:403
Code: ff df e8 47 c1 4a 00 49 8d 5f 08 48 89 d8 48 c1 e8 03 48 89 44 24 10 80 3c 28 00 74 08 48 89 df e8 49 0c a2 00 48 89 5c 24 18 <4d> 8b 77 08 49 8d 5f 10 49 89 dd 49 c1 ed 03 41 80 7c 2d 00 00 74
RSP: 0018:ffffc90002e27478 EFLAGS: 00000246
RAX: 1ffff920005c4eb6 RBX: ffffc90002e275b0 RCX: ffff88801af48000
RDX: 0000000000000000 RSI: ffffc90002e27da8 RDI: ffffc90002e275a8
RBP: dffffc0000000000 R08: ffff88801af48000 R09: 0000000000000003
R10: 0000000000000004 R11: 0000000000000000 R12: ffffc90002e275a8
R13: dffffc0000000000 R14: ffffffff8ece8a94 R15: ffffc90002e275a8
FS: 0000000000000000(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055555a6b85c8 CR3: 000000000cb30000 CR4: 00000000003506f0
Call Trace:
<TASK>
unwind_next_frame+0x1789/0x2970 arch/x86/kernel/unwind_orc.c:648
arch_stack_walk+0x144/0x190 arch/x86/kernel/stacktrace.c:25
stack_trace_save+0x9c/0xe0 kernel/stacktrace.c:122
kasan_save_stack mm/kasan/common.c:45 [inline]
kasan_set_track+0x4e/0x70 mm/kasan/common.c:52
kasan_save_free_info+0x2e/0x50 mm/kasan/generic.c:522
____kasan_slab_free+0x126/0x1e0 mm/kasan/common.c:236
kasan_slab_free include/linux/kasan.h:164 [inline]
slab_free_hook mm/slub.c:1811 [inline]
slab_free_freelist_hook+0x130/0x1b0 mm/slub.c:1837
slab_free mm/slub.c:3830 [inline]
__kmem_cache_free+0xba/0x1f0 mm/slub.c:3843
skb_kfree_head net/core/skbuff.c:945 [inline]
skb_free_head net/core/skbuff.c:957 [inline]
skb_release_data+0x634/0x800 net/core/skbuff.c:987
skb_release_all net/core/skbuff.c:1053 [inline]
__kfree_skb net/core/skbuff.c:1067 [inline]
consume_skb+0xb2/0x110 net/core/skbuff.c:1283
nsim_dev_trap_report drivers/net/netdevsim/dev.c:821 [inline]
nsim_dev_trap_report_work+0x76f/0xb00 drivers/net/netdevsim/dev.c:851
process_one_work kernel/workqueue.c:2634 [inline]
process_scheduled_works+0xa45/0x15b0 kernel/workqueue.c:2711
worker_thread+0xa55/0xfc0 kernel/workqueue.c:2792
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>
---
If you want syzbot to run the reproducer, reply with:
process_scheduled_works+0xa45/0x15b0 kernel/workqueue.c:2711
worker_thread+0xa55/0xfc0 kernel/workqueue.c:2792
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>
---
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
Reply all
Reply to author
Forward
0 new messages