[v6.6] INFO: task hung in deactivate_super
0 views
Skip to first unread message
syzbot
12:24 PM (8 hours ago) 12:24 PM
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: c56aaf1a85ae Linux 6.6.123
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=162497fa580000
kernel config: https://syzkaller.appspot.com/x/.config?x=2a950bf7c0bff9f9
dashboard link: https://syzkaller.appspot.com/bug?extid=6523e68e66606c1b250f
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/0c1480594070/disk-c56aaf1a.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/118e64c14227/vmlinux-c56aaf1a.xz
kernel image: https://storage.googleapis.com/syzbot-assets/320a7e9bfff1/bzImage-c56aaf1a.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+6523e6...@syzkaller.appspotmail.com
INFO: task syz-executor:24692 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:21704 pid:24692 ppid:1 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5381 [inline]
__schedule+0x1553/0x45a0 kernel/sched/core.c:6700
schedule+0xbd/0x170 kernel/sched/core.c:6774
schedule_preempt_disabled+0x13/0x20 kernel/sched/core.c:6833
rwsem_down_write_slowpath+0xc05/0xff0 kernel/locking/rwsem.c:1178
__down_write_common kernel/locking/rwsem.c:1306 [inline]
__down_write kernel/locking/rwsem.c:1315 [inline]
down_write+0x1b9/0x200 kernel/locking/rwsem.c:1574
__super_lock fs/super.c:56 [inline]
__super_lock_excl fs/super.c:71 [inline]
deactivate_super+0xa4/0xe0 fs/super.c:513
cleanup_mnt+0x43b/0x4d0 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/0xa0 arch/x86/entry/common.c:82
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f652279c1d7
RSP: 002b:00007fffc7bd9e28 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 00007f6522830b3b RCX: 00007f652279c1d7
RDX: 0000000000000000 RSI: 0000000000000009 RDI: 00007fffc7bd9ee0
RBP: 00007fffc7bd9ee0 R08: 00007fffc7bdaee0 R09: 00000000ffffffff
R10: 0000000000000000 R11: 0000000000000246 R12: 00007fffc7bdaf70
R13: 00007f6522830b3b R14: 00000000001af5f3 R15: 00007fffc7bdafb0
</TASK>
INFO: task syz.0.3839:24997 blocked for more than 145 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.0.3839 state:D stack:26568 pid:24997 ppid:24565 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5381 [inline]
__schedule+0x1553/0x45a0 kernel/sched/core.c:6700
schedule+0xbd/0x170 kernel/sched/core.c:6774
wb_wait_for_completion+0x173/0x2a0 fs/fs-writeback.c:192
sync_inodes_sb+0x1c9/0xa10 fs/fs-writeback.c:2778
iterate_supers+0xb2/0x170 fs/super.c:979
ksys_sync+0xa1/0x170 fs/sync.c:102
__ia32_sys_sync+0xe/0x20 fs/sync.c:113
do_syscall_x64 arch/x86/entry/common.c:46 [inline]
do_syscall_64+0x55/0xa0 arch/x86/entry/common.c:76
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f4024f9af79
RSP: 002b:00007f4025d72028 EFLAGS: 00000246 ORIG_RAX: 00000000000000a2
RAX: ffffffffffffffda RBX: 00007f4025215fa0 RCX: 00007f4024f9af79
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 00007f4025215fa0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f4025216038 R14: 00007f4025215fa0 R15: 00007ffeecec36f8
</TASK>
Showing all locks held in the system:
1 lock held by khungtaskd/29:
#0: ffffffff8d131fe0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:334 [inline]
#0: ffffffff8d131fe0 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:786 [inline]
#0: ffffffff8d131fe0 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x55/0x290 kernel/locking/lockdep.c:6633
5 locks held by kworker/u4:6/1292:
3 locks held by kworker/u4:13/13330:
2 locks held by kworker/1:3/14936:
#0: ffff888017c72538 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2609 [inline]
#0: ffff888017c72538 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_scheduled_works+0x96f/0x15d0 kernel/workqueue.c:2711
#1: ffffc9000348fd00 ((work_completion)(&rew->rew_work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2609 [inline]
#1: ffffc9000348fd00 ((work_completion)(&rew->rew_work)){+.+.}-{0:0}, at: process_scheduled_works+0x96f/0x15d0 kernel/workqueue.c:2711
2 locks held by getty/24175:
#0: ffff88802d60d0a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:243
#1: ffffc9000e02d2f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x433/0x1390 drivers/tty/n_tty.c:2217
1 lock held by syz-executor/24692:
#0: ffff88807e67a0e0 (&type->s_umount_key#32){++++}-{3:3}, at: __super_lock fs/super.c:56 [inline]
#0: ffff88807e67a0e0 (&type->s_umount_key#32){++++}-{3:3}, at: __super_lock_excl fs/super.c:71 [inline]
#0: ffff88807e67a0e0 (&type->s_umount_key#32){++++}-{3:3}, at: deactivate_super+0xa4/0xe0 fs/super.c:513
2 locks held by syz.0.3839/24997:
#0: ffff88807e67a0e0 (&type->s_umount_key#32){++++}-{3:3}, at: __super_lock fs/super.c:58 [inline]
#0: ffff88807e67a0e0 (&type->s_umount_key#32){++++}-{3:3}, at: super_lock+0x17f/0x3a0 fs/super.c:117
#1: ffff888021a3c7d0 (&bdi->wb_switch_rwsem){+.+.}-{3:3}, at: bdi_down_write_wb_switch_rwsem fs/fs-writeback.c:364 [inline]
#1: ffff888021a3c7d0 (&bdi->wb_switch_rwsem){+.+.}-{3:3}, at: sync_inodes_sb+0x1ad/0xa10 fs/fs-writeback.c:2776
1 lock held by syz-executor/25372:
#0: ffffffff8d1379b8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:292 [inline]
#0: ffffffff8d1379b8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x306/0x880 kernel/rcu/tree_exp.h:1004
1 lock held by syz-executor/26203:
#0: ffffffff8d1379b8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:324 [inline]
#0: ffffffff8d1379b8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x3da/0x880 kernel/rcu/tree_exp.h:1004
2 locks held by sed/27277:
=============================================
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 01/24/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+0xf3d/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: 13330 Comm: kworker/u4:13 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/24/2026
Workqueue: events_unbound nsim_dev_trap_report_work
RIP: 0010:__lock_acquire+0x12f0/0x7d40 kernel/locking/lockdep.c:5134
Code: 31 db 48 83 c3 40 48 89 d8 48 c1 e8 03 42 80 3c 00 00 74 12 48 89 df e8 ee 03 77 00 49 b8 00 00 00 00 00 fc ff df 48 83 3b 00 <0f> 84 55 4c 00 00 49 c1 e4 20 48 8b 44 24 48 42 0f b6 04 00 84 c0
RSP: 0018:ffffc900044674e0 EFLAGS: 00000082
RAX: 1ffffffff2165346 RBX: ffffffff90b29a30 RCX: ffffffff81683943
RDX: 0000000000000000 RSI: 0000000000000008 RDI: ffffffff911bf500
RBP: ffffc90004467728 R08: dffffc0000000000 R09: 1ffffffff2237ea0
R10: dffffc0000000000 R11: fffffbfff2237ea1 R12: 000000004e06280c
R13: ffff88802a02bc00 R14: 000000000d6be41c R15: ffff88802a02c7a0
FS: 0000000000000000(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fa76430d7d0 CR3: 000000002d336000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 000000000000e58e DR6: 00000000ffff0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
lock_acquire+0x19e/0x420 kernel/locking/lockdep.c:5754
local_lock_acquire include/linux/local_lock_internal.h:29 [inline]
crng_make_state+0x15f/0x700 drivers/char/random.c:347
_get_random_bytes+0x100/0x250 drivers/char/random.c:385
eth_random_addr include/linux/etherdevice.h:232 [inline]
nsim_dev_trap_skb_build drivers/net/netdevsim/dev.c:755 [inline]
nsim_dev_trap_report drivers/net/netdevsim/dev.c:805 [inline]
nsim_dev_trap_report_work+0x338/0xb00 drivers/net/netdevsim/dev.c:851
process_one_work kernel/workqueue.c:2634 [inline]
process_scheduled_works+0xa5d/0x15d0 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: c56aaf1a85ae Linux 6.6.123
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=162497fa580000
kernel config: https://syzkaller.appspot.com/x/.config?x=2a950bf7c0bff9f9
dashboard link: https://syzkaller.appspot.com/bug?extid=6523e68e66606c1b250f
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/0c1480594070/disk-c56aaf1a.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/118e64c14227/vmlinux-c56aaf1a.xz
kernel image: https://storage.googleapis.com/syzbot-assets/320a7e9bfff1/bzImage-c56aaf1a.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+6523e6...@syzkaller.appspotmail.com
INFO: task syz-executor:24692 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:21704 pid:24692 ppid:1 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5381 [inline]
__schedule+0x1553/0x45a0 kernel/sched/core.c:6700
schedule+0xbd/0x170 kernel/sched/core.c:6774
schedule_preempt_disabled+0x13/0x20 kernel/sched/core.c:6833
rwsem_down_write_slowpath+0xc05/0xff0 kernel/locking/rwsem.c:1178
__down_write_common kernel/locking/rwsem.c:1306 [inline]
__down_write kernel/locking/rwsem.c:1315 [inline]
down_write+0x1b9/0x200 kernel/locking/rwsem.c:1574
__super_lock fs/super.c:56 [inline]
__super_lock_excl fs/super.c:71 [inline]
deactivate_super+0xa4/0xe0 fs/super.c:513
cleanup_mnt+0x43b/0x4d0 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/0xa0 arch/x86/entry/common.c:82
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f652279c1d7
RSP: 002b:00007fffc7bd9e28 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 00007f6522830b3b RCX: 00007f652279c1d7
RDX: 0000000000000000 RSI: 0000000000000009 RDI: 00007fffc7bd9ee0
RBP: 00007fffc7bd9ee0 R08: 00007fffc7bdaee0 R09: 00000000ffffffff
R10: 0000000000000000 R11: 0000000000000246 R12: 00007fffc7bdaf70
R13: 00007f6522830b3b R14: 00000000001af5f3 R15: 00007fffc7bdafb0
</TASK>
INFO: task syz.0.3839:24997 blocked for more than 145 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.0.3839 state:D stack:26568 pid:24997 ppid:24565 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5381 [inline]
__schedule+0x1553/0x45a0 kernel/sched/core.c:6700
schedule+0xbd/0x170 kernel/sched/core.c:6774
wb_wait_for_completion+0x173/0x2a0 fs/fs-writeback.c:192
sync_inodes_sb+0x1c9/0xa10 fs/fs-writeback.c:2778
iterate_supers+0xb2/0x170 fs/super.c:979
ksys_sync+0xa1/0x170 fs/sync.c:102
__ia32_sys_sync+0xe/0x20 fs/sync.c:113
do_syscall_x64 arch/x86/entry/common.c:46 [inline]
do_syscall_64+0x55/0xa0 arch/x86/entry/common.c:76
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f4024f9af79
RSP: 002b:00007f4025d72028 EFLAGS: 00000246 ORIG_RAX: 00000000000000a2
RAX: ffffffffffffffda RBX: 00007f4025215fa0 RCX: 00007f4024f9af79
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 00007f4025215fa0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f4025216038 R14: 00007f4025215fa0 R15: 00007ffeecec36f8
</TASK>
Showing all locks held in the system:
1 lock held by khungtaskd/29:
#0: ffffffff8d131fe0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:334 [inline]
#0: ffffffff8d131fe0 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:786 [inline]
#0: ffffffff8d131fe0 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x55/0x290 kernel/locking/lockdep.c:6633
5 locks held by kworker/u4:6/1292:
3 locks held by kworker/u4:13/13330:
2 locks held by kworker/1:3/14936:
#0: ffff888017c72538 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2609 [inline]
#0: ffff888017c72538 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_scheduled_works+0x96f/0x15d0 kernel/workqueue.c:2711
#1: ffffc9000348fd00 ((work_completion)(&rew->rew_work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2609 [inline]
#1: ffffc9000348fd00 ((work_completion)(&rew->rew_work)){+.+.}-{0:0}, at: process_scheduled_works+0x96f/0x15d0 kernel/workqueue.c:2711
2 locks held by getty/24175:
#0: ffff88802d60d0a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:243
#1: ffffc9000e02d2f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x433/0x1390 drivers/tty/n_tty.c:2217
1 lock held by syz-executor/24692:
#0: ffff88807e67a0e0 (&type->s_umount_key#32){++++}-{3:3}, at: __super_lock fs/super.c:56 [inline]
#0: ffff88807e67a0e0 (&type->s_umount_key#32){++++}-{3:3}, at: __super_lock_excl fs/super.c:71 [inline]
#0: ffff88807e67a0e0 (&type->s_umount_key#32){++++}-{3:3}, at: deactivate_super+0xa4/0xe0 fs/super.c:513
2 locks held by syz.0.3839/24997:
#0: ffff88807e67a0e0 (&type->s_umount_key#32){++++}-{3:3}, at: __super_lock fs/super.c:58 [inline]
#0: ffff88807e67a0e0 (&type->s_umount_key#32){++++}-{3:3}, at: super_lock+0x17f/0x3a0 fs/super.c:117
#1: ffff888021a3c7d0 (&bdi->wb_switch_rwsem){+.+.}-{3:3}, at: bdi_down_write_wb_switch_rwsem fs/fs-writeback.c:364 [inline]
#1: ffff888021a3c7d0 (&bdi->wb_switch_rwsem){+.+.}-{3:3}, at: sync_inodes_sb+0x1ad/0xa10 fs/fs-writeback.c:2776
1 lock held by syz-executor/25372:
#0: ffffffff8d1379b8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:292 [inline]
#0: ffffffff8d1379b8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x306/0x880 kernel/rcu/tree_exp.h:1004
1 lock held by syz-executor/26203:
#0: ffffffff8d1379b8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:324 [inline]
#0: ffffffff8d1379b8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x3da/0x880 kernel/rcu/tree_exp.h:1004
2 locks held by sed/27277:
=============================================
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 01/24/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+0xf3d/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: 13330 Comm: kworker/u4:13 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/24/2026
Workqueue: events_unbound nsim_dev_trap_report_work
RIP: 0010:__lock_acquire+0x12f0/0x7d40 kernel/locking/lockdep.c:5134
Code: 31 db 48 83 c3 40 48 89 d8 48 c1 e8 03 42 80 3c 00 00 74 12 48 89 df e8 ee 03 77 00 49 b8 00 00 00 00 00 fc ff df 48 83 3b 00 <0f> 84 55 4c 00 00 49 c1 e4 20 48 8b 44 24 48 42 0f b6 04 00 84 c0
RSP: 0018:ffffc900044674e0 EFLAGS: 00000082
RAX: 1ffffffff2165346 RBX: ffffffff90b29a30 RCX: ffffffff81683943
RDX: 0000000000000000 RSI: 0000000000000008 RDI: ffffffff911bf500
RBP: ffffc90004467728 R08: dffffc0000000000 R09: 1ffffffff2237ea0
R10: dffffc0000000000 R11: fffffbfff2237ea1 R12: 000000004e06280c
R13: ffff88802a02bc00 R14: 000000000d6be41c R15: ffff88802a02c7a0
FS: 0000000000000000(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fa76430d7d0 CR3: 000000002d336000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 000000000000e58e DR6: 00000000ffff0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
lock_acquire+0x19e/0x420 kernel/locking/lockdep.c:5754
local_lock_acquire include/linux/local_lock_internal.h:29 [inline]
crng_make_state+0x15f/0x700 drivers/char/random.c:347
_get_random_bytes+0x100/0x250 drivers/char/random.c:385
eth_random_addr include/linux/etherdevice.h:232 [inline]
nsim_dev_trap_skb_build drivers/net/netdevsim/dev.c:755 [inline]
nsim_dev_trap_report drivers/net/netdevsim/dev.c:805 [inline]
nsim_dev_trap_report_work+0x338/0xb00 drivers/net/netdevsim/dev.c:851
process_one_work kernel/workqueue.c:2634 [inline]
process_scheduled_works+0xa5d/0x15d0 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
Reply all
Reply to author
Forward
0 new messages