[v5.15] INFO: task hung in mpol_rebind_mm
0 views
Skip to first unread message
syzbot
Sep 28, 2025, 6:17:32 PMSep 28
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 43bb85222e53 Linux 5.15.193
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=10825ae2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=e1bb6d24ef2164eb
dashboard link: https://syzkaller.appspot.com/bug?extid=bbd2c8637e67cf4b529c
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=11ed0334580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14cecae2580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/0bc183664ae8/disk-43bb8522.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/0fc2f6618934/vmlinux-43bb8522.xz
kernel image: https://storage.googleapis.com/syzbot-assets/af70b3957f4c/bzImage-43bb8522.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+bbd2c8...@syzkaller.appspotmail.com
INFO: task syz-executor:4327 blocked for more than 143 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor state:D stack:21352 pid: 4327 ppid: 4317 flags:0x00004000
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]
mpol_rebind_mm+0x33/0x2c0 mm/mempolicy.c:381
cpuset_attach+0x330/0x5f0 kernel/cgroup/cpuset.c:2376
cgroup_migrate_execute+0x7eb/0x1010 kernel/cgroup/cgroup.c:2574
cgroup_attach_task+0x562/0x7e0 kernel/cgroup/cgroup.c:2869
__cgroup1_procs_write+0x2e5/0x3f0 kernel/cgroup/cgroup-v1.c:527
cgroup_file_write+0x2f7/0x630 kernel/cgroup/cgroup.c:3943
kernfs_fop_write_iter+0x379/0x4c0 fs/kernfs/file.c:296
call_write_iter include/linux/fs.h:2172 [inline]
new_sync_write fs/read_write.c:507 [inline]
vfs_write+0x712/0xd00 fs/read_write.c:594
ksys_write+0x14d/0x250 fs/read_write.c:647
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:0x7fead48b297f
RSP: 002b:00007ffe2c76fd40 EFLAGS: 00000293 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007fead48b297f
RDX: 0000000000000001 RSI: 00007ffe2c76fd90 RDI: 0000000000000003
RBP: 00007ffe2c770300 R08: 0000000000000000 R09: 00007ffe2c76fb97
R10: 0000000000000000 R11: 0000000000000293 R12: 0000000000000001
R13: 00007ffe2c76fd90 R14: 00007ffe2c7702c0 R15: 00007ffe2c770300
</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/3854:
#0: ffffffff8c1420f0 (cgroup_threadgroup_rwsem){++++}-{0:0}, at: copy_process+0x2290/0x3e00 kernel/fork.c:2382
2 locks held by getty/3946:
#0: ffff88814cee5098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
#1: ffffc90002cf62e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x5ba/0x1a30 drivers/tty/n_tty.c:2158
1 lock held by udevd/4227:
#0: ffffffff8c1420f0 (cgroup_threadgroup_rwsem){++++}-{0:0}, at: do_exit+0x256/0x20a0 kernel/exit.c:830
1 lock held by udevd/4244:
#0: ffff888016869628 (&mm->mmap_lock){++++}-{3:3}, at: mmap_write_lock_killable include/linux/mmap_lock.h:87 [inline]
#0: ffff888016869628 (&mm->mmap_lock){++++}-{3:3}, at: __vm_munmap+0xf3/0x230 mm/mmap.c:2949
1 lock held by udevd/4245:
#0: ffffffff8c1420f0 (cgroup_threadgroup_rwsem){++++}-{0:0}, at: do_exit+0x256/0x20a0 kernel/exit.c:830
1 lock held by udevd/4246:
#0: ffffffff8c1420f0 (cgroup_threadgroup_rwsem){++++}-{0:0}, at: do_exit+0x256/0x20a0 kernel/exit.c:830
1 lock held by syz-executor/4319:
#0: ffffffff8c1420f0 (cgroup_threadgroup_rwsem){++++}-{0:0}, at: do_exit+0x256/0x20a0 kernel/exit.c:830
2 locks held by syz-executor/4321:
#0: ffffffff8c1a66f0 (dup_mmap_sem){.+.+}-{0:0}, at: dup_mmap kernel/fork.c:503 [inline]
#0: ffffffff8c1a66f0 (dup_mmap_sem){.+.+}-{0:0}, at: dup_mm kernel/fork.c:1466 [inline]
#0: ffffffff8c1a66f0 (dup_mmap_sem){.+.+}-{0:0}, at: copy_mm+0x21f/0x1380 kernel/fork.c:1518
#1: ffff88802ba92428 (&mm->mmap_lock){++++}-{3:3}, at: mmap_write_lock_killable include/linux/mmap_lock.h:87 [inline]
#1: ffff88802ba92428 (&mm->mmap_lock){++++}-{3:3}, at: dup_mmap kernel/fork.c:504 [inline]
#1: ffff88802ba92428 (&mm->mmap_lock){++++}-{3:3}, at: dup_mm kernel/fork.c:1466 [inline]
#1: ffff88802ba92428 (&mm->mmap_lock){++++}-{3:3}, at: copy_mm+0x238/0x1380 kernel/fork.c:1518
2 locks held by syz-executor/4322:
#0: ffffffff8c1a66f0 (dup_mmap_sem){.+.+}-{0:0}, at: dup_mmap kernel/fork.c:503 [inline]
#0: ffffffff8c1a66f0 (dup_mmap_sem){.+.+}-{0:0}, at: dup_mm kernel/fork.c:1466 [inline]
#0: ffffffff8c1a66f0 (dup_mmap_sem){.+.+}-{0:0}, at: copy_mm+0x21f/0x1380 kernel/fork.c:1518
#1: ffff88802ba94728 (&mm->mmap_lock){++++}-{3:3}, at: mmap_write_lock_killable include/linux/mmap_lock.h:87 [inline]
#1: ffff88802ba94728 (&mm->mmap_lock){++++}-{3:3}, at: dup_mmap kernel/fork.c:504 [inline]
#1: ffff88802ba94728 (&mm->mmap_lock){++++}-{3:3}, at: dup_mm kernel/fork.c:1466 [inline]
#1: ffff88802ba94728 (&mm->mmap_lock){++++}-{3:3}, at: copy_mm+0x238/0x1380 kernel/fork.c:1518
7 locks held by syz-executor/4327:
#0: ffff888019386460 (sb_writers#11){.+.+}-{0:0}, at: vfs_write+0x28a/0xd00 fs/read_write.c:590
#1: ffff88805cc01888 (&of->mutex){+.+.}-{3:3}, at: kernfs_fop_write_iter+0x1e5/0x4c0 fs/kernfs/file.c:287
#2: ffffffff8c141f08 (cgroup_mutex){+.+.}-{3:3}, at: cgroup_kn_lock_live+0xee/0x230 kernel/cgroup/cgroup.c:1639
#3: ffffffff8bfbadd0 (cpu_hotplug_lock){++++}-{0:0}, at: cgroup_attach_lock kernel/cgroup/cgroup.c:2388 [inline]
#3: ffffffff8bfbadd0 (cpu_hotplug_lock){++++}-{0:0}, at: cgroup_procs_write_start+0x17c/0x580 kernel/cgroup/cgroup.c:2898
#4: ffffffff8c1420f0 (cgroup_threadgroup_rwsem){++++}-{0:0}, at: cgroup_attach_lock kernel/cgroup/cgroup.c:2390 [inline]
#4: ffffffff8c1420f0 (cgroup_threadgroup_rwsem){++++}-{0:0}, at: cgroup_procs_write_start+0x192/0x580 kernel/cgroup/cgroup.c:2898
#5: ffffffff8c14f948 (cpuset_mutex){+.+.}-{3:3}, at: cpuset_attach+0xac/0x5f0 kernel/cgroup/cpuset.c:2348
#6: ffff88802ba92b28 (&mm->mmap_lock){++++}-{3:3}, at: mmap_write_lock include/linux/mmap_lock.h:71 [inline]
#6: ffff88802ba92b28 (&mm->mmap_lock){++++}-{3:3}, at: mpol_rebind_mm+0x33/0x2c0 mm/mempolicy.c:381
2 locks held by syz-executor/4329:
#0: ffffffff8c1a66f0 (dup_mmap_sem){.+.+}-{0:0}, at: dup_mmap kernel/fork.c:503 [inline]
#0: ffffffff8c1a66f0 (dup_mmap_sem){.+.+}-{0:0}, at: dup_mm kernel/fork.c:1466 [inline]
#0: ffffffff8c1a66f0 (dup_mmap_sem){.+.+}-{0:0}, at: copy_mm+0x21f/0x1380 kernel/fork.c:1518
#1: ffff88802ba96328 (&mm->mmap_lock){++++}-{3:3}, at: mmap_write_lock_killable include/linux/mmap_lock.h:87 [inline]
#1: ffff88802ba96328 (&mm->mmap_lock){++++}-{3:3}, at: dup_mmap kernel/fork.c:504 [inline]
#1: ffff88802ba96328 (&mm->mmap_lock){++++}-{3:3}, at: dup_mm kernel/fork.c:1466 [inline]
#1: ffff88802ba96328 (&mm->mmap_lock){++++}-{3:3}, at: copy_mm+0x238/0x1380 kernel/fork.c:1518
2 locks held by syz-executor/4330:
#0: ffffffff8c1a66f0 (dup_mmap_sem){.+.+}-{0:0}, at: dup_mmap kernel/fork.c:503 [inline]
#0: ffffffff8c1a66f0 (dup_mmap_sem){.+.+}-{0:0}, at: dup_mm kernel/fork.c:1466 [inline]
#0: ffffffff8c1a66f0 (dup_mmap_sem){.+.+}-{0:0}, at: copy_mm+0x21f/0x1380 kernel/fork.c:1518
#1: ffff88802ba97128 (&mm->mmap_lock){++++}-{3:3}, at: mmap_write_lock_killable include/linux/mmap_lock.h:87 [inline]
#1: ffff88802ba97128 (&mm->mmap_lock){++++}-{3:3}, at: dup_mmap kernel/fork.c:504 [inline]
#1: ffff88802ba97128 (&mm->mmap_lock){++++}-{3:3}, at: dup_mm kernel/fork.c:1466 [inline]
#1: ffff88802ba97128 (&mm->mmap_lock){++++}-{3:3}, at: copy_mm+0x238/0x1380 kernel/fork.c:1518
=============================================
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: 144 Comm: kworker/u4:1 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025
Workqueue: bat_events batadv_nc_worker
RIP: 0010:check_kcov_mode kernel/kcov.c:183 [inline]
RIP: 0010:write_comp_data kernel/kcov.c:227 [inline]
RIP: 0010:__sanitizer_cov_trace_const_cmp4+0x32/0x80 kernel/kcov.c:293
Code: 34 a1 8a 7e 65 8b 15 35 a1 8a 7e 81 e2 00 01 ff 00 74 11 81 fa 00 01 00 00 75 5b 83 b9 34 16 00 00 00 74 52 8b 91 10 16 00 00 <83> fa 03 75 47 48 8b 91 18 16 00 00 44 8b 89 14 16 00 00 49 c1 e1
RSP: 0018:ffffc9000155fa88 EFLAGS: 00000046
RAX: ffffffff817de966 RBX: 0000000000000001 RCX: ffff88801b9e8000
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000
RBP: ffffc9000155fb38 R08: dffffc0000000000 R09: ffffed100ba53ae9
R10: ffffed100ba53ae9 R11: 1ffff1100ba53ae8 R12: ffffffff897ea836
R13: dffffc0000000000 R14: dffffc0000000000 R15: 1ffff920002abf54
FS: 0000000000000000(0000) GS:ffff8880b9100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f43a38b59c0 CR3: 000000007e79c000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
trace_hardirqs_on+0x16/0x80 kernel/trace/trace_preemptirq.c:42
__local_bh_enable_ip+0x12a/0x1b0 kernel/softirq.c:406
spin_unlock_bh include/linux/spinlock.h:408 [inline]
batadv_nc_purge_paths+0x316/0x3b0 net/batman-adv/network-coding.c:475
batadv_nc_worker+0x2e7/0x5c0 net/batman-adv/network-coding.c:724
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 syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
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: 43bb85222e53 Linux 5.15.193
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=10825ae2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=e1bb6d24ef2164eb
dashboard link: https://syzkaller.appspot.com/bug?extid=bbd2c8637e67cf4b529c
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=11ed0334580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14cecae2580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/0bc183664ae8/disk-43bb8522.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/0fc2f6618934/vmlinux-43bb8522.xz
kernel image: https://storage.googleapis.com/syzbot-assets/af70b3957f4c/bzImage-43bb8522.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+bbd2c8...@syzkaller.appspotmail.com
INFO: task syz-executor:4327 blocked for more than 143 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor state:D stack:21352 pid: 4327 ppid: 4317 flags:0x00004000
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]
mpol_rebind_mm+0x33/0x2c0 mm/mempolicy.c:381
cpuset_attach+0x330/0x5f0 kernel/cgroup/cpuset.c:2376
cgroup_migrate_execute+0x7eb/0x1010 kernel/cgroup/cgroup.c:2574
cgroup_attach_task+0x562/0x7e0 kernel/cgroup/cgroup.c:2869
__cgroup1_procs_write+0x2e5/0x3f0 kernel/cgroup/cgroup-v1.c:527
cgroup_file_write+0x2f7/0x630 kernel/cgroup/cgroup.c:3943
kernfs_fop_write_iter+0x379/0x4c0 fs/kernfs/file.c:296
call_write_iter include/linux/fs.h:2172 [inline]
new_sync_write fs/read_write.c:507 [inline]
vfs_write+0x712/0xd00 fs/read_write.c:594
ksys_write+0x14d/0x250 fs/read_write.c:647
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:0x7fead48b297f
RSP: 002b:00007ffe2c76fd40 EFLAGS: 00000293 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007fead48b297f
RDX: 0000000000000001 RSI: 00007ffe2c76fd90 RDI: 0000000000000003
RBP: 00007ffe2c770300 R08: 0000000000000000 R09: 00007ffe2c76fb97
R10: 0000000000000000 R11: 0000000000000293 R12: 0000000000000001
R13: 00007ffe2c76fd90 R14: 00007ffe2c7702c0 R15: 00007ffe2c770300
</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/3854:
#0: ffffffff8c1420f0 (cgroup_threadgroup_rwsem){++++}-{0:0}, at: copy_process+0x2290/0x3e00 kernel/fork.c:2382
2 locks held by getty/3946:
#0: ffff88814cee5098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
#1: ffffc90002cf62e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x5ba/0x1a30 drivers/tty/n_tty.c:2158
1 lock held by udevd/4227:
#0: ffffffff8c1420f0 (cgroup_threadgroup_rwsem){++++}-{0:0}, at: do_exit+0x256/0x20a0 kernel/exit.c:830
1 lock held by udevd/4244:
#0: ffff888016869628 (&mm->mmap_lock){++++}-{3:3}, at: mmap_write_lock_killable include/linux/mmap_lock.h:87 [inline]
#0: ffff888016869628 (&mm->mmap_lock){++++}-{3:3}, at: __vm_munmap+0xf3/0x230 mm/mmap.c:2949
1 lock held by udevd/4245:
#0: ffffffff8c1420f0 (cgroup_threadgroup_rwsem){++++}-{0:0}, at: do_exit+0x256/0x20a0 kernel/exit.c:830
1 lock held by udevd/4246:
#0: ffffffff8c1420f0 (cgroup_threadgroup_rwsem){++++}-{0:0}, at: do_exit+0x256/0x20a0 kernel/exit.c:830
1 lock held by syz-executor/4319:
#0: ffffffff8c1420f0 (cgroup_threadgroup_rwsem){++++}-{0:0}, at: do_exit+0x256/0x20a0 kernel/exit.c:830
2 locks held by syz-executor/4321:
#0: ffffffff8c1a66f0 (dup_mmap_sem){.+.+}-{0:0}, at: dup_mmap kernel/fork.c:503 [inline]
#0: ffffffff8c1a66f0 (dup_mmap_sem){.+.+}-{0:0}, at: dup_mm kernel/fork.c:1466 [inline]
#0: ffffffff8c1a66f0 (dup_mmap_sem){.+.+}-{0:0}, at: copy_mm+0x21f/0x1380 kernel/fork.c:1518
#1: ffff88802ba92428 (&mm->mmap_lock){++++}-{3:3}, at: mmap_write_lock_killable include/linux/mmap_lock.h:87 [inline]
#1: ffff88802ba92428 (&mm->mmap_lock){++++}-{3:3}, at: dup_mmap kernel/fork.c:504 [inline]
#1: ffff88802ba92428 (&mm->mmap_lock){++++}-{3:3}, at: dup_mm kernel/fork.c:1466 [inline]
#1: ffff88802ba92428 (&mm->mmap_lock){++++}-{3:3}, at: copy_mm+0x238/0x1380 kernel/fork.c:1518
2 locks held by syz-executor/4322:
#0: ffffffff8c1a66f0 (dup_mmap_sem){.+.+}-{0:0}, at: dup_mmap kernel/fork.c:503 [inline]
#0: ffffffff8c1a66f0 (dup_mmap_sem){.+.+}-{0:0}, at: dup_mm kernel/fork.c:1466 [inline]
#0: ffffffff8c1a66f0 (dup_mmap_sem){.+.+}-{0:0}, at: copy_mm+0x21f/0x1380 kernel/fork.c:1518
#1: ffff88802ba94728 (&mm->mmap_lock){++++}-{3:3}, at: mmap_write_lock_killable include/linux/mmap_lock.h:87 [inline]
#1: ffff88802ba94728 (&mm->mmap_lock){++++}-{3:3}, at: dup_mmap kernel/fork.c:504 [inline]
#1: ffff88802ba94728 (&mm->mmap_lock){++++}-{3:3}, at: dup_mm kernel/fork.c:1466 [inline]
#1: ffff88802ba94728 (&mm->mmap_lock){++++}-{3:3}, at: copy_mm+0x238/0x1380 kernel/fork.c:1518
7 locks held by syz-executor/4327:
#0: ffff888019386460 (sb_writers#11){.+.+}-{0:0}, at: vfs_write+0x28a/0xd00 fs/read_write.c:590
#1: ffff88805cc01888 (&of->mutex){+.+.}-{3:3}, at: kernfs_fop_write_iter+0x1e5/0x4c0 fs/kernfs/file.c:287
#2: ffffffff8c141f08 (cgroup_mutex){+.+.}-{3:3}, at: cgroup_kn_lock_live+0xee/0x230 kernel/cgroup/cgroup.c:1639
#3: ffffffff8bfbadd0 (cpu_hotplug_lock){++++}-{0:0}, at: cgroup_attach_lock kernel/cgroup/cgroup.c:2388 [inline]
#3: ffffffff8bfbadd0 (cpu_hotplug_lock){++++}-{0:0}, at: cgroup_procs_write_start+0x17c/0x580 kernel/cgroup/cgroup.c:2898
#4: ffffffff8c1420f0 (cgroup_threadgroup_rwsem){++++}-{0:0}, at: cgroup_attach_lock kernel/cgroup/cgroup.c:2390 [inline]
#4: ffffffff8c1420f0 (cgroup_threadgroup_rwsem){++++}-{0:0}, at: cgroup_procs_write_start+0x192/0x580 kernel/cgroup/cgroup.c:2898
#5: ffffffff8c14f948 (cpuset_mutex){+.+.}-{3:3}, at: cpuset_attach+0xac/0x5f0 kernel/cgroup/cpuset.c:2348
#6: ffff88802ba92b28 (&mm->mmap_lock){++++}-{3:3}, at: mmap_write_lock include/linux/mmap_lock.h:71 [inline]
#6: ffff88802ba92b28 (&mm->mmap_lock){++++}-{3:3}, at: mpol_rebind_mm+0x33/0x2c0 mm/mempolicy.c:381
2 locks held by syz-executor/4329:
#0: ffffffff8c1a66f0 (dup_mmap_sem){.+.+}-{0:0}, at: dup_mmap kernel/fork.c:503 [inline]
#0: ffffffff8c1a66f0 (dup_mmap_sem){.+.+}-{0:0}, at: dup_mm kernel/fork.c:1466 [inline]
#0: ffffffff8c1a66f0 (dup_mmap_sem){.+.+}-{0:0}, at: copy_mm+0x21f/0x1380 kernel/fork.c:1518
#1: ffff88802ba96328 (&mm->mmap_lock){++++}-{3:3}, at: mmap_write_lock_killable include/linux/mmap_lock.h:87 [inline]
#1: ffff88802ba96328 (&mm->mmap_lock){++++}-{3:3}, at: dup_mmap kernel/fork.c:504 [inline]
#1: ffff88802ba96328 (&mm->mmap_lock){++++}-{3:3}, at: dup_mm kernel/fork.c:1466 [inline]
#1: ffff88802ba96328 (&mm->mmap_lock){++++}-{3:3}, at: copy_mm+0x238/0x1380 kernel/fork.c:1518
2 locks held by syz-executor/4330:
#0: ffffffff8c1a66f0 (dup_mmap_sem){.+.+}-{0:0}, at: dup_mmap kernel/fork.c:503 [inline]
#0: ffffffff8c1a66f0 (dup_mmap_sem){.+.+}-{0:0}, at: dup_mm kernel/fork.c:1466 [inline]
#0: ffffffff8c1a66f0 (dup_mmap_sem){.+.+}-{0:0}, at: copy_mm+0x21f/0x1380 kernel/fork.c:1518
#1: ffff88802ba97128 (&mm->mmap_lock){++++}-{3:3}, at: mmap_write_lock_killable include/linux/mmap_lock.h:87 [inline]
#1: ffff88802ba97128 (&mm->mmap_lock){++++}-{3:3}, at: dup_mmap kernel/fork.c:504 [inline]
#1: ffff88802ba97128 (&mm->mmap_lock){++++}-{3:3}, at: dup_mm kernel/fork.c:1466 [inline]
#1: ffff88802ba97128 (&mm->mmap_lock){++++}-{3:3}, at: copy_mm+0x238/0x1380 kernel/fork.c:1518
=============================================
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: 144 Comm: kworker/u4:1 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025
Workqueue: bat_events batadv_nc_worker
RIP: 0010:check_kcov_mode kernel/kcov.c:183 [inline]
RIP: 0010:write_comp_data kernel/kcov.c:227 [inline]
RIP: 0010:__sanitizer_cov_trace_const_cmp4+0x32/0x80 kernel/kcov.c:293
Code: 34 a1 8a 7e 65 8b 15 35 a1 8a 7e 81 e2 00 01 ff 00 74 11 81 fa 00 01 00 00 75 5b 83 b9 34 16 00 00 00 74 52 8b 91 10 16 00 00 <83> fa 03 75 47 48 8b 91 18 16 00 00 44 8b 89 14 16 00 00 49 c1 e1
RSP: 0018:ffffc9000155fa88 EFLAGS: 00000046
RAX: ffffffff817de966 RBX: 0000000000000001 RCX: ffff88801b9e8000
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000
RBP: ffffc9000155fb38 R08: dffffc0000000000 R09: ffffed100ba53ae9
R10: ffffed100ba53ae9 R11: 1ffff1100ba53ae8 R12: ffffffff897ea836
R13: dffffc0000000000 R14: dffffc0000000000 R15: 1ffff920002abf54
FS: 0000000000000000(0000) GS:ffff8880b9100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f43a38b59c0 CR3: 000000007e79c000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
trace_hardirqs_on+0x16/0x80 kernel/trace/trace_preemptirq.c:42
__local_bh_enable_ip+0x12a/0x1b0 kernel/softirq.c:406
spin_unlock_bh include/linux/spinlock.h:408 [inline]
batadv_nc_purge_paths+0x316/0x3b0 net/batman-adv/network-coding.c:475
batadv_nc_worker+0x2e7/0x5c0 net/batman-adv/network-coding.c:724
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 syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
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