[v5.15] INFO: task hung in exit_mm
1 view
Skip to first unread message
syzbot
Oct 8, 2025, 12:39:36 PM (8 days ago) Oct 8
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 29e53a5b1c4f Linux 5.15.194
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=166c11e2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=e1bb6d24ef2164eb
dashboard link: https://syzkaller.appspot.com/bug?extid=1fccef9498203420f8ab
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/8cd4e3ff852c/disk-29e53a5b.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/21e1f773622c/vmlinux-29e53a5b.xz
kernel image: https://storage.googleapis.com/syzbot-assets/8f418c0a25cc/bzImage-29e53a5b.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+1fccef...@syzkaller.appspotmail.com
INFO: task syz.2.3269:21012 blocked for more than 143 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.2.3269 state:D stack:25344 pid:21012 ppid: 11530 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5049 [inline]
__schedule+0x11bb/0x4390 kernel/sched/core.c:6395
schedule+0x11b/0x1e0 kernel/sched/core.c:6478
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6537
rwsem_down_read_slowpath+0x528/0x990 kernel/locking/rwsem.c:1055
__down_read_common kernel/locking/rwsem.c:1239 [inline]
__down_read kernel/locking/rwsem.c:1252 [inline]
down_read+0x96/0x2e0 kernel/locking/rwsem.c:1500
mmap_read_lock include/linux/mmap_lock.h:117 [inline]
exit_mm+0xda/0x6c0 kernel/exit.c:499
do_exit+0x5a1/0x20a0 kernel/exit.c:870
do_group_exit+0x12e/0x300 kernel/exit.c:997
get_signal+0x6ca/0x12c0 kernel/signal.c:2900
arch_do_signal_or_restart+0xc1/0x1300 arch/x86/kernel/signal.c:867
handle_signal_work kernel/entry/common.c:154 [inline]
exit_to_user_mode_loop+0x9e/0x130 kernel/entry/common.c:178
exit_to_user_mode_prepare+0xee/0x180 kernel/entry/common.c:214
__syscall_exit_to_user_mode_work kernel/entry/common.c:296 [inline]
syscall_exit_to_user_mode+0x16/0x40 kernel/entry/common.c:307
do_syscall_64+0x58/0xa0 arch/x86/entry/common.c:86
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f8ad5480f03
RSP: 002b:00007ffddbdde258 EFLAGS: 00000246 ORIG_RAX: 0000000000000009
RAX: fffffffffffffffc RBX: 00007f8ad3ee96c0 RCX: 00007f8ad5480f03
RDX: 0000000000000000 RSI: 0000000000021000 RDI: 0000000000000000
RBP: 0000000000000000 R08: 00000000ffffffff R09: 0000000000000000
R10: 0000000000020022 R11: 0000000000000246 R12: 00007ffddbdde3b0
R13: ffffffffffffffc0 R14: 0000000000001000 R15: 0000000000000000
</TASK>
INFO: task syz.2.3269:21013 blocked for more than 143 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.2.3269 state:D stack:24136 pid:21013 ppid: 11530 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5049 [inline]
__schedule+0x11bb/0x4390 kernel/sched/core.c:6395
schedule+0x11b/0x1e0 kernel/sched/core.c:6478
rwsem_down_write_slowpath+0xc46/0x11f0 kernel/locking/rwsem.c:1165
mmap_write_lock include/linux/mmap_lock.h:71 [inline]
mmu_notifier_register+0x27/0xa0 mm/mmu_notifier.c:727
kvm_init_mmu_notifier virt/kvm/kvm_main.c:862 [inline]
kvm_create_vm virt/kvm/kvm_main.c:1156 [inline]
kvm_dev_ioctl_create_vm virt/kvm/kvm_main.c:4754 [inline]
kvm_dev_ioctl+0x13ac/0x2040 virt/kvm/kvm_main.c:4809
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:874 [inline]
__se_sys_ioctl+0xfa/0x170 fs/ioctl.c:860
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f8ad5480ec9
RSP: 002b:00007f8ad36e8038 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f8ad56d7fa0 RCX: 00007f8ad5480ec9
RDX: 0000000000000000 RSI: 000000000000ae01 RDI: 0000000000000008
RBP: 00007f8ad5503f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f8ad56d8038 R14: 00007f8ad56d7fa0 R15: 00007ffddbdde2b8
</TASK>
Showing all locks held in the system:
1 lock held by khungtaskd/27:
#0: ffffffff8c11c660 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
1 lock held by dhcpcd/3855:
#0: ffff88807e486a28 (&mm->mmap_lock){++++}-{3:3}, at: mmap_write_lock_killable include/linux/mmap_lock.h:87 [inline]
#0: ffff88807e486a28 (&mm->mmap_lock){++++}-{3:3}, at: vm_mmap_pgoff+0x15d/0x2b0 mm/util.c:549
2 locks held by getty/3948:
#0: ffff88802bd63098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
#1: ffffc900026562e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x5ba/0x1a30 drivers/tty/n_tty.c:2158
1 lock held by syz-executor/4173:
#0: ffff888079c68128 (&mm->mmap_lock){++++}-{3:3}, at: mmap_write_lock_killable include/linux/mmap_lock.h:87 [inline]
#0: ffff888079c68128 (&mm->mmap_lock){++++}-{3:3}, at: vm_mmap_pgoff+0x15d/0x2b0 mm/util.c:549
1 lock held by udevd/4334:
#0: ffff88801ea0d528 (&mm->mmap_lock){++++}-{3:3}, at: mmap_write_lock_killable include/linux/mmap_lock.h:87 [inline]
#0: ffff88801ea0d528 (&mm->mmap_lock){++++}-{3:3}, at: vm_mmap_pgoff+0x15d/0x2b0 mm/util.c:549
2 locks held by syz-executor/6595:
#0: ffffffff8c1a67f0 (dup_mmap_sem){.+.+}-{0:0}, at: dup_mmap kernel/fork.c:503 [inline]
#0: ffffffff8c1a67f0 (dup_mmap_sem){.+.+}-{0:0}, at: dup_mm kernel/fork.c:1466 [inline]
#0: ffffffff8c1a67f0 (dup_mmap_sem){.+.+}-{0:0}, at: copy_mm+0x21f/0x1380 kernel/fork.c:1518
#1: ffff88801e82f128 (&mm->mmap_lock){++++}-{3:3}, at: mmap_write_lock_killable include/linux/mmap_lock.h:87 [inline]
#1: ffff88801e82f128 (&mm->mmap_lock){++++}-{3:3}, at: dup_mmap kernel/fork.c:504 [inline]
#1: ffff88801e82f128 (&mm->mmap_lock){++++}-{3:3}, at: dup_mm kernel/fork.c:1466 [inline]
#1: ffff88801e82f128 (&mm->mmap_lock){++++}-{3:3}, at: copy_mm+0x238/0x1380 kernel/fork.c:1518
2 locks held by syz-executor/9367:
#0: ffffffff8c1a67f0 (dup_mmap_sem){.+.+}-{0:0}, at: dup_mmap kernel/fork.c:503 [inline]
#0: ffffffff8c1a67f0 (dup_mmap_sem){.+.+}-{0:0}, at: dup_mm kernel/fork.c:1466 [inline]
#0: ffffffff8c1a67f0 (dup_mmap_sem){.+.+}-{0:0}, at: copy_mm+0x21f/0x1380 kernel/fork.c:1518
#1: ffff888079c6b928 (&mm->mmap_lock){++++}-{3:3}, at: mmap_write_lock_killable include/linux/mmap_lock.h:87 [inline]
#1: ffff888079c6b928 (&mm->mmap_lock){++++}-{3:3}, at: dup_mmap kernel/fork.c:504 [inline]
#1: ffff888079c6b928 (&mm->mmap_lock){++++}-{3:3}, at: dup_mm kernel/fork.c:1466 [inline]
#1: ffff888079c6b928 (&mm->mmap_lock){++++}-{3:3}, at: copy_mm+0x238/0x1380 kernel/fork.c:1518
1 lock held by udevd/15177:
#0: ffff888079c6c028 (&mm->mmap_lock){++++}-{3:3}, at: mmap_write_lock_killable include/linux/mmap_lock.h:87 [inline]
#0: ffff888079c6c028 (&mm->mmap_lock){++++}-{3:3}, at: do_mprotect_pkey+0x173/0x910 mm/mprotect.c:551
2 locks held by syz-executor/18901:
#0: ffffffff8c1a67f0 (dup_mmap_sem){.+.+}-{0:0}, at: dup_mmap kernel/fork.c:503 [inline]
#0: ffffffff8c1a67f0 (dup_mmap_sem){.+.+}-{0:0}, at: dup_mm kernel/fork.c:1466 [inline]
#0: ffffffff8c1a67f0 (dup_mmap_sem){.+.+}-{0:0}, at: copy_mm+0x21f/0x1380 kernel/fork.c:1518
#1: ffff8880756bb228 (&mm->mmap_lock){++++}-{3:3}, at: mmap_write_lock_killable include/linux/mmap_lock.h:87 [inline]
#1: ffff8880756bb228 (&mm->mmap_lock){++++}-{3:3}, at: dup_mmap kernel/fork.c:504 [inline]
#1: ffff8880756bb228 (&mm->mmap_lock){++++}-{3:3}, at: dup_mm kernel/fork.c:1466 [inline]
#1: ffff8880756bb228 (&mm->mmap_lock){++++}-{3:3}, at: copy_mm+0x238/0x1380 kernel/fork.c:1518
2 locks held by syz-executor/20256:
#0: ffffffff8c1a67f0 (dup_mmap_sem){.+.+}-{0:0}, at: dup_mmap kernel/fork.c:503 [inline]
#0: ffffffff8c1a67f0 (dup_mmap_sem){.+.+}-{0:0}, at: dup_mm kernel/fork.c:1466 [inline]
#0: ffffffff8c1a67f0 (dup_mmap_sem){.+.+}-{0:0}, at: copy_mm+0x21f/0x1380 kernel/fork.c:1518
#1: ffff88807e514728 (&mm->mmap_lock){++++}-{3:3}, at: mmap_write_lock_killable include/linux/mmap_lock.h:87 [inline]
#1: ffff88807e514728 (&mm->mmap_lock){++++}-{3:3}, at: dup_mmap kernel/fork.c:504 [inline]
#1: ffff88807e514728 (&mm->mmap_lock){++++}-{3:3}, at: dup_mm kernel/fork.c:1466 [inline]
#1: ffff88807e514728 (&mm->mmap_lock){++++}-{3:3}, at: copy_mm+0x238/0x1380 kernel/fork.c:1518
1 lock held by syz.2.3269/21012:
#0: ffff8880754d6a28 (&mm->mmap_lock){++++}-{3:3}, at: mmap_read_lock include/linux/mmap_lock.h:117 [inline]
#0: ffff8880754d6a28 (&mm->mmap_lock){++++}-{3:3}, at: exit_mm+0xda/0x6c0 kernel/exit.c:499
1 lock held by syz.2.3269/21013:
#0: ffff8880754d6a28 (&mm->mmap_lock){++++}-{3:3}, at: mmap_write_lock include/linux/mmap_lock.h:71 [inline]
#0: ffff8880754d6a28 (&mm->mmap_lock){++++}-{3:3}, at: mmu_notifier_register+0x27/0xa0 mm/mmu_notifier.c:727
=============================================
NMI backtrace for cpu 0
CPU: 0 PID: 27 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+0x168/0x230 lib/dump_stack.c:106
nmi_cpu_backtrace+0x397/0x3d0 lib/nmi_backtrace.c:111
nmi_trigger_cpumask_backtrace+0x163/0x280 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:212 [inline]
watchdog+0xe0f/0xe50 kernel/hung_task.c:369
kthread+0x436/0x520 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 4299 Comm: kworker/1:8 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025
Workqueue: events nsim_dev_trap_report_work
RIP: 0010:kasan_check_range+0x1ab/0x290 mm/kasan/generic.c:-1
Code: 4d 89 d6 4d 8d 56 07 4d 85 f6 4d 0f 49 d6 49 83 e2 f8 4d 29 d6 74 12 41 80 39 00 0f 85 a0 00 00 00 49 ff c1 49 ff ce 75 ee 5b <41> 5e 41 5f c3 84 db 75 61 f7 c3 00 ff 00 00 75 5e f7 c3 00 00 ff
RSP: 0018:ffffc9000341f530 EFLAGS: 00000256
RAX: 0000000000000001 RBX: 0000000000000010 RCX: ffffffff8134829d
RDX: 0000000000000001 RSI: 0000000000000010 RDI: ffffc9000341f678
RBP: 0000000000000000 R08: dffffc0000000000 R09: fffff52000683ed1
R10: fffff52000683ed1 R11: 1ffff92000683ecf R12: 1ffffffff1cb09ca
R13: dffffc0000000000 R14: 0000000000000002 R15: dffffc0000000001
FS: 0000000000000000(0000) GS:ffff8880b9100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f13bf6ce6e1 CR3: 000000002b81c000 CR4: 00000000003526e0
Call Trace:
<TASK>
memset+0x1e/0x40 mm/kasan/shadow.c:44
unwind_next_frame+0xa3d/0x1d90 arch/x86/kernel/unwind_orc.c:547
arch_stack_walk+0x10c/0x140 arch/x86/kernel/stacktrace.c:25
stack_trace_save+0x98/0xe0 kernel/stacktrace.c:122
kasan_save_stack mm/kasan/common.c:38 [inline]
kasan_set_track+0x4b/0x70 mm/kasan/common.c:46
kasan_set_free_info+0x1f/0x40 mm/kasan/generic.c:360
____kasan_slab_free+0xd5/0x110 mm/kasan/common.c:366
kasan_slab_free include/linux/kasan.h:230 [inline]
slab_free_hook mm/slub.c:1710 [inline]
slab_free_freelist_hook+0xea/0x170 mm/slub.c:1736
slab_free mm/slub.c:3504 [inline]
kfree+0xef/0x2a0 mm/slub.c:4564
skb_free_head net/core/skbuff.c:655 [inline]
skb_release_data+0x6fe/0x850 net/core/skbuff.c:677
skb_release_all net/core/skbuff.c:742 [inline]
__kfree_skb net/core/skbuff.c:756 [inline]
consume_skb+0xa2/0x100 net/core/skbuff.c:914
nsim_dev_trap_report drivers/net/netdevsim/dev.c:737 [inline]
nsim_dev_trap_report_work+0x7cb/0xb40 drivers/net/netdevsim/dev.c:762
process_one_work+0x863/0x1000 kernel/workqueue.c:2310
worker_thread+0xaa8/0x12a0 kernel/workqueue.c:2457
kthread+0x436/0x520 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</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: 29e53a5b1c4f Linux 5.15.194
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=166c11e2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=e1bb6d24ef2164eb
dashboard link: https://syzkaller.appspot.com/bug?extid=1fccef9498203420f8ab
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/8cd4e3ff852c/disk-29e53a5b.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/21e1f773622c/vmlinux-29e53a5b.xz
kernel image: https://storage.googleapis.com/syzbot-assets/8f418c0a25cc/bzImage-29e53a5b.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+1fccef...@syzkaller.appspotmail.com
INFO: task syz.2.3269:21012 blocked for more than 143 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.2.3269 state:D stack:25344 pid:21012 ppid: 11530 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5049 [inline]
__schedule+0x11bb/0x4390 kernel/sched/core.c:6395
schedule+0x11b/0x1e0 kernel/sched/core.c:6478
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6537
rwsem_down_read_slowpath+0x528/0x990 kernel/locking/rwsem.c:1055
__down_read_common kernel/locking/rwsem.c:1239 [inline]
__down_read kernel/locking/rwsem.c:1252 [inline]
down_read+0x96/0x2e0 kernel/locking/rwsem.c:1500
mmap_read_lock include/linux/mmap_lock.h:117 [inline]
exit_mm+0xda/0x6c0 kernel/exit.c:499
do_exit+0x5a1/0x20a0 kernel/exit.c:870
do_group_exit+0x12e/0x300 kernel/exit.c:997
get_signal+0x6ca/0x12c0 kernel/signal.c:2900
arch_do_signal_or_restart+0xc1/0x1300 arch/x86/kernel/signal.c:867
handle_signal_work kernel/entry/common.c:154 [inline]
exit_to_user_mode_loop+0x9e/0x130 kernel/entry/common.c:178
exit_to_user_mode_prepare+0xee/0x180 kernel/entry/common.c:214
__syscall_exit_to_user_mode_work kernel/entry/common.c:296 [inline]
syscall_exit_to_user_mode+0x16/0x40 kernel/entry/common.c:307
do_syscall_64+0x58/0xa0 arch/x86/entry/common.c:86
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f8ad5480f03
RSP: 002b:00007ffddbdde258 EFLAGS: 00000246 ORIG_RAX: 0000000000000009
RAX: fffffffffffffffc RBX: 00007f8ad3ee96c0 RCX: 00007f8ad5480f03
RDX: 0000000000000000 RSI: 0000000000021000 RDI: 0000000000000000
RBP: 0000000000000000 R08: 00000000ffffffff R09: 0000000000000000
R10: 0000000000020022 R11: 0000000000000246 R12: 00007ffddbdde3b0
R13: ffffffffffffffc0 R14: 0000000000001000 R15: 0000000000000000
</TASK>
INFO: task syz.2.3269:21013 blocked for more than 143 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.2.3269 state:D stack:24136 pid:21013 ppid: 11530 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5049 [inline]
__schedule+0x11bb/0x4390 kernel/sched/core.c:6395
schedule+0x11b/0x1e0 kernel/sched/core.c:6478
rwsem_down_write_slowpath+0xc46/0x11f0 kernel/locking/rwsem.c:1165
mmap_write_lock include/linux/mmap_lock.h:71 [inline]
mmu_notifier_register+0x27/0xa0 mm/mmu_notifier.c:727
kvm_init_mmu_notifier virt/kvm/kvm_main.c:862 [inline]
kvm_create_vm virt/kvm/kvm_main.c:1156 [inline]
kvm_dev_ioctl_create_vm virt/kvm/kvm_main.c:4754 [inline]
kvm_dev_ioctl+0x13ac/0x2040 virt/kvm/kvm_main.c:4809
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:874 [inline]
__se_sys_ioctl+0xfa/0x170 fs/ioctl.c:860
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f8ad5480ec9
RSP: 002b:00007f8ad36e8038 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f8ad56d7fa0 RCX: 00007f8ad5480ec9
RDX: 0000000000000000 RSI: 000000000000ae01 RDI: 0000000000000008
RBP: 00007f8ad5503f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f8ad56d8038 R14: 00007f8ad56d7fa0 R15: 00007ffddbdde2b8
</TASK>
Showing all locks held in the system:
1 lock held by khungtaskd/27:
#0: ffffffff8c11c660 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
1 lock held by dhcpcd/3855:
#0: ffff88807e486a28 (&mm->mmap_lock){++++}-{3:3}, at: mmap_write_lock_killable include/linux/mmap_lock.h:87 [inline]
#0: ffff88807e486a28 (&mm->mmap_lock){++++}-{3:3}, at: vm_mmap_pgoff+0x15d/0x2b0 mm/util.c:549
2 locks held by getty/3948:
#0: ffff88802bd63098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
#1: ffffc900026562e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x5ba/0x1a30 drivers/tty/n_tty.c:2158
1 lock held by syz-executor/4173:
#0: ffff888079c68128 (&mm->mmap_lock){++++}-{3:3}, at: mmap_write_lock_killable include/linux/mmap_lock.h:87 [inline]
#0: ffff888079c68128 (&mm->mmap_lock){++++}-{3:3}, at: vm_mmap_pgoff+0x15d/0x2b0 mm/util.c:549
1 lock held by udevd/4334:
#0: ffff88801ea0d528 (&mm->mmap_lock){++++}-{3:3}, at: mmap_write_lock_killable include/linux/mmap_lock.h:87 [inline]
#0: ffff88801ea0d528 (&mm->mmap_lock){++++}-{3:3}, at: vm_mmap_pgoff+0x15d/0x2b0 mm/util.c:549
2 locks held by syz-executor/6595:
#0: ffffffff8c1a67f0 (dup_mmap_sem){.+.+}-{0:0}, at: dup_mmap kernel/fork.c:503 [inline]
#0: ffffffff8c1a67f0 (dup_mmap_sem){.+.+}-{0:0}, at: dup_mm kernel/fork.c:1466 [inline]
#0: ffffffff8c1a67f0 (dup_mmap_sem){.+.+}-{0:0}, at: copy_mm+0x21f/0x1380 kernel/fork.c:1518
#1: ffff88801e82f128 (&mm->mmap_lock){++++}-{3:3}, at: mmap_write_lock_killable include/linux/mmap_lock.h:87 [inline]
#1: ffff88801e82f128 (&mm->mmap_lock){++++}-{3:3}, at: dup_mmap kernel/fork.c:504 [inline]
#1: ffff88801e82f128 (&mm->mmap_lock){++++}-{3:3}, at: dup_mm kernel/fork.c:1466 [inline]
#1: ffff88801e82f128 (&mm->mmap_lock){++++}-{3:3}, at: copy_mm+0x238/0x1380 kernel/fork.c:1518
2 locks held by syz-executor/9367:
#0: ffffffff8c1a67f0 (dup_mmap_sem){.+.+}-{0:0}, at: dup_mmap kernel/fork.c:503 [inline]
#0: ffffffff8c1a67f0 (dup_mmap_sem){.+.+}-{0:0}, at: dup_mm kernel/fork.c:1466 [inline]
#0: ffffffff8c1a67f0 (dup_mmap_sem){.+.+}-{0:0}, at: copy_mm+0x21f/0x1380 kernel/fork.c:1518
#1: ffff888079c6b928 (&mm->mmap_lock){++++}-{3:3}, at: mmap_write_lock_killable include/linux/mmap_lock.h:87 [inline]
#1: ffff888079c6b928 (&mm->mmap_lock){++++}-{3:3}, at: dup_mmap kernel/fork.c:504 [inline]
#1: ffff888079c6b928 (&mm->mmap_lock){++++}-{3:3}, at: dup_mm kernel/fork.c:1466 [inline]
#1: ffff888079c6b928 (&mm->mmap_lock){++++}-{3:3}, at: copy_mm+0x238/0x1380 kernel/fork.c:1518
1 lock held by udevd/15177:
#0: ffff888079c6c028 (&mm->mmap_lock){++++}-{3:3}, at: mmap_write_lock_killable include/linux/mmap_lock.h:87 [inline]
#0: ffff888079c6c028 (&mm->mmap_lock){++++}-{3:3}, at: do_mprotect_pkey+0x173/0x910 mm/mprotect.c:551
2 locks held by syz-executor/18901:
#0: ffffffff8c1a67f0 (dup_mmap_sem){.+.+}-{0:0}, at: dup_mmap kernel/fork.c:503 [inline]
#0: ffffffff8c1a67f0 (dup_mmap_sem){.+.+}-{0:0}, at: dup_mm kernel/fork.c:1466 [inline]
#0: ffffffff8c1a67f0 (dup_mmap_sem){.+.+}-{0:0}, at: copy_mm+0x21f/0x1380 kernel/fork.c:1518
#1: ffff8880756bb228 (&mm->mmap_lock){++++}-{3:3}, at: mmap_write_lock_killable include/linux/mmap_lock.h:87 [inline]
#1: ffff8880756bb228 (&mm->mmap_lock){++++}-{3:3}, at: dup_mmap kernel/fork.c:504 [inline]
#1: ffff8880756bb228 (&mm->mmap_lock){++++}-{3:3}, at: dup_mm kernel/fork.c:1466 [inline]
#1: ffff8880756bb228 (&mm->mmap_lock){++++}-{3:3}, at: copy_mm+0x238/0x1380 kernel/fork.c:1518
2 locks held by syz-executor/20256:
#0: ffffffff8c1a67f0 (dup_mmap_sem){.+.+}-{0:0}, at: dup_mmap kernel/fork.c:503 [inline]
#0: ffffffff8c1a67f0 (dup_mmap_sem){.+.+}-{0:0}, at: dup_mm kernel/fork.c:1466 [inline]
#0: ffffffff8c1a67f0 (dup_mmap_sem){.+.+}-{0:0}, at: copy_mm+0x21f/0x1380 kernel/fork.c:1518
#1: ffff88807e514728 (&mm->mmap_lock){++++}-{3:3}, at: mmap_write_lock_killable include/linux/mmap_lock.h:87 [inline]
#1: ffff88807e514728 (&mm->mmap_lock){++++}-{3:3}, at: dup_mmap kernel/fork.c:504 [inline]
#1: ffff88807e514728 (&mm->mmap_lock){++++}-{3:3}, at: dup_mm kernel/fork.c:1466 [inline]
#1: ffff88807e514728 (&mm->mmap_lock){++++}-{3:3}, at: copy_mm+0x238/0x1380 kernel/fork.c:1518
1 lock held by syz.2.3269/21012:
#0: ffff8880754d6a28 (&mm->mmap_lock){++++}-{3:3}, at: mmap_read_lock include/linux/mmap_lock.h:117 [inline]
#0: ffff8880754d6a28 (&mm->mmap_lock){++++}-{3:3}, at: exit_mm+0xda/0x6c0 kernel/exit.c:499
1 lock held by syz.2.3269/21013:
#0: ffff8880754d6a28 (&mm->mmap_lock){++++}-{3:3}, at: mmap_write_lock include/linux/mmap_lock.h:71 [inline]
#0: ffff8880754d6a28 (&mm->mmap_lock){++++}-{3:3}, at: mmu_notifier_register+0x27/0xa0 mm/mmu_notifier.c:727
=============================================
NMI backtrace for cpu 0
CPU: 0 PID: 27 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+0x168/0x230 lib/dump_stack.c:106
nmi_cpu_backtrace+0x397/0x3d0 lib/nmi_backtrace.c:111
nmi_trigger_cpumask_backtrace+0x163/0x280 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:212 [inline]
watchdog+0xe0f/0xe50 kernel/hung_task.c:369
kthread+0x436/0x520 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 4299 Comm: kworker/1:8 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025
Workqueue: events nsim_dev_trap_report_work
RIP: 0010:kasan_check_range+0x1ab/0x290 mm/kasan/generic.c:-1
Code: 4d 89 d6 4d 8d 56 07 4d 85 f6 4d 0f 49 d6 49 83 e2 f8 4d 29 d6 74 12 41 80 39 00 0f 85 a0 00 00 00 49 ff c1 49 ff ce 75 ee 5b <41> 5e 41 5f c3 84 db 75 61 f7 c3 00 ff 00 00 75 5e f7 c3 00 00 ff
RSP: 0018:ffffc9000341f530 EFLAGS: 00000256
RAX: 0000000000000001 RBX: 0000000000000010 RCX: ffffffff8134829d
RDX: 0000000000000001 RSI: 0000000000000010 RDI: ffffc9000341f678
RBP: 0000000000000000 R08: dffffc0000000000 R09: fffff52000683ed1
R10: fffff52000683ed1 R11: 1ffff92000683ecf R12: 1ffffffff1cb09ca
R13: dffffc0000000000 R14: 0000000000000002 R15: dffffc0000000001
FS: 0000000000000000(0000) GS:ffff8880b9100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f13bf6ce6e1 CR3: 000000002b81c000 CR4: 00000000003526e0
Call Trace:
<TASK>
memset+0x1e/0x40 mm/kasan/shadow.c:44
unwind_next_frame+0xa3d/0x1d90 arch/x86/kernel/unwind_orc.c:547
arch_stack_walk+0x10c/0x140 arch/x86/kernel/stacktrace.c:25
stack_trace_save+0x98/0xe0 kernel/stacktrace.c:122
kasan_save_stack mm/kasan/common.c:38 [inline]
kasan_set_track+0x4b/0x70 mm/kasan/common.c:46
kasan_set_free_info+0x1f/0x40 mm/kasan/generic.c:360
____kasan_slab_free+0xd5/0x110 mm/kasan/common.c:366
kasan_slab_free include/linux/kasan.h:230 [inline]
slab_free_hook mm/slub.c:1710 [inline]
slab_free_freelist_hook+0xea/0x170 mm/slub.c:1736
slab_free mm/slub.c:3504 [inline]
kfree+0xef/0x2a0 mm/slub.c:4564
skb_free_head net/core/skbuff.c:655 [inline]
skb_release_data+0x6fe/0x850 net/core/skbuff.c:677
skb_release_all net/core/skbuff.c:742 [inline]
__kfree_skb net/core/skbuff.c:756 [inline]
consume_skb+0xa2/0x100 net/core/skbuff.c:914
nsim_dev_trap_report drivers/net/netdevsim/dev.c:737 [inline]
nsim_dev_trap_report_work+0x7cb/0xb40 drivers/net/netdevsim/dev.c:762
process_one_work+0x863/0x1000 kernel/workqueue.c:2310
worker_thread+0xaa8/0x12a0 kernel/workqueue.c:2457
kthread+0x436/0x520 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</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