Hello,
syzbot found the following issue on:
HEAD commit: 8ce36b2849ef Linux 6.1.163
git tree: linux-6.1.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=1621e652580000
kernel config:
https://syzkaller.appspot.com/x/.config?x=f0605c5af04d7603
dashboard link:
https://syzkaller.appspot.com/bug?extid=3c81872f733ce5dfedf7
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/25d3bb1313db/disk-8ce36b28.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/53d3c77e16da/vmlinux-8ce36b28.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/ca171a78e481/bzImage-8ce36b28.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+3c8187...@syzkaller.appspotmail.com
rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
rcu: Tasks blocked on level-0 rcu_node (CPUs 0-1): P6000/1:b..l P4285/1:b..l P4520/1:b..l
(detected by 0, t=10502 jiffies, g=34129, q=177 ncpus=2)
task:udevd state:R running task stack:23472 pid:4520 ppid:3639 flags:0x00004002
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5245 [inline]
__schedule+0x11d1/0x40e0 kernel/sched/core.c:6562
preempt_schedule_common+0x82/0xd0 kernel/sched/core.c:6731
preempt_schedule+0xbc/0xd0 kernel/sched/core.c:6755
preempt_schedule_thunk+0x16/0x18 arch/x86/entry/thunk_64.S:34
__raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:152 [inline]
_raw_spin_unlock_irqrestore+0x10d/0x120 kernel/locking/spinlock.c:194
spin_unlock_irqrestore include/linux/spinlock.h:406 [inline]
__wake_up_common_lock kernel/sched/wait.c:140 [inline]
__wake_up_sync_key+0x128/0x190 kernel/sched/wait.c:208
sock_def_readable+0x15b/0x280 net/core/sock.c:3316
unix_dgram_sendmsg+0x1051/0x16e0 net/unix/af_unix.c:2085
sock_sendmsg_nosec net/socket.c:718 [inline]
__sock_sendmsg net/socket.c:730 [inline]
sock_write_iter+0x2d9/0x3e0 net/socket.c:1143
call_write_iter include/linux/fs.h:2265 [inline]
new_sync_write fs/read_write.c:491 [inline]
vfs_write+0x4b1/0xa30 fs/read_write.c:584
ksys_write+0x14c/0x250 fs/read_write.c:637
do_syscall_x64 arch/x86/entry/common.c:46 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fc1a62a7407
RSP: 002b:00007ffc78c6bea0 EFLAGS: 00000202 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007fc1a6a4a880 RCX: 00007fc1a62a7407
RDX: 0000000000000000 RSI: 00007ffc78c6bf47 RDI: 000000000000000a
RBP: 000000000000000a R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000202 R12: 00007fc1a6a4a6e8
R13: 0000000000000000 R14: 0000000000000000 R15: 00005570abe7a010
</TASK>
task:udevd state:R running task stack:22512 pid:4285 ppid:3639 flags:0x00004002
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5245 [inline]
__schedule+0x11d1/0x40e0 kernel/sched/core.c:6562
preempt_schedule_irq+0xbb/0x160 kernel/sched/core.c:6874
irqentry_exit+0x63/0x70 kernel/entry/common.c:439
asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:691
RIP: 0010:lock_acquire+0x225/0x4a0 kernel/locking/lockdep.c:5666
Code: f7 84 24 80 00 00 00 00 02 00 00 43 c6 44 3d 04 f8 0f 85 f0 00 00 00 41 f7 c6 00 02 00 00 74 01 fb 48 c7 44 24 60 0e 36 e0 45 <4b> c7 44 3d 00 00 00 00 00 43 c7 44 3d 08 00 00 00 00 65 48 8b 04
RSP: 0018:ffffc90003de7700 EFLAGS: 00000206
RAX: 0000000000000001 RBX: 0000000000000000 RCX: 01fcba4bad7bc800
RDX: 0000000000000000 RSI: ffffffff8a8c23a0 RDI: ffffffff8adf0d20
RBP: ffffc90003de7818 R08: dffffc0000000000 R09: 1ffffffff215ea48
R10: dffffc0000000000 R11: fffffbfff215ea49 R12: 0000000000000001
R13: 1ffff920007bceec R14: 0000000000000246 R15: dffffc0000000000
rcu_lock_acquire include/linux/rcupdate.h:350 [inline]
rcu_read_lock include/linux/rcupdate.h:791 [inline]
is_bpf_text_address+0x43/0x2a0 kernel/bpf/core.c:735
kernel_text_address+0x9c/0xd0 kernel/extable.c:125
__kernel_text_address+0x9/0x30 kernel/extable.c:79
unwind_get_return_address+0x49/0x80 arch/x86/kernel/unwind_orc.c:323
arch_stack_walk+0xf2/0x140 arch/x86/kernel/stacktrace.c:26
stack_trace_save+0xa6/0xf0 kernel/stacktrace.c:122
kasan_save_stack mm/kasan/common.c:46 [inline]
kasan_set_track+0x4b/0x70 mm/kasan/common.c:53
kasan_save_free_info+0x2d/0x50 mm/kasan/generic.c:516
____kasan_slab_free+0x126/0x1e0 mm/kasan/common.c:237
kasan_slab_free include/linux/kasan.h:177 [inline]
slab_free_hook mm/slub.c:1729 [inline]
slab_free_freelist_hook+0x131/0x1a0 mm/slub.c:1755
slab_free mm/slub.c:3687 [inline]
kmem_cache_free+0xf7/0x290 mm/slub.c:3709
do_renameat2+0xc49/0xce0 fs/namei.c:5060
__do_sys_rename fs/namei.c:5081 [inline]
__se_sys_rename fs/namei.c:5079 [inline]
__x64_sys_rename+0x82/0x90 fs/namei.c:5079
do_syscall_x64 arch/x86/entry/common.c:46 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fc1a627acc7
RSP: 002b:00007ffc78c69c08 EFLAGS: 00000202 ORIG_RAX: 0000000000000052
RAX: ffffffffffffffda RBX: 00005570abe266e0 RCX: 00007fc1a627acc7
RDX: 0000000000000000 RSI: 00005570abe266e0 RDI: 00007ffc78c6a0c0
RBP: 00005570abe266fc R08: 00007ffc78c6a0c0 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000202 R12: 00007ffc78c6a0c0
R13: 00007ffc78c69cc0 R14: 000055709049f6d7 R15: 00007ffc78c6ad50
</TASK>
task:kworker/u4:18 state:R running task stack:22168 pid:6000 ppid:2 flags:0x00004000
Workqueue: bat_events batadv_nc_worker
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5245 [inline]
__schedule+0x11d1/0x40e0 kernel/sched/core.c:6562
preempt_schedule_irq+0xbb/0x160 kernel/sched/core.c:6874
irqentry_exit+0x63/0x70 kernel/entry/common.c:439
asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:691
RIP: 0010:lock_acquire+0x225/0x4a0 kernel/locking/lockdep.c:5666
Code: f7 84 24 80 00 00 00 00 02 00 00 43 c6 44 3d 04 f8 0f 85 f0 00 00 00 41 f7 c6 00 02 00 00 74 01 fb 48 c7 44 24 60 0e 36 e0 45 <4b> c7 44 3d 00 00 00 00 00 43 c7 44 3d 08 00 00 00 00 65 48 8b 04
RSP: 0018:ffffc90005297ac0 EFLAGS: 00000206
RAX: 0000000000000001 RBX: 0000000000000000 RCX: 38a4f53ab72c2900
RDX: 0000000000000000 RSI: ffffffff8a8c23a0 RDI: ffffffff8adf0d20
RBP: ffffc90005297bc8 R08: dffffc0000000000 R09: 1ffffffff215ea48
R10: dffffc0000000000 R11: fffffbfff215ea49 R12: 0000000000000001
R13: 1ffff92000a52f64 R14: 0000000000000246 R15: dffffc0000000000
rcu_lock_acquire include/linux/rcupdate.h:350 [inline]
rcu_read_lock include/linux/rcupdate.h:791 [inline]
batadv_nc_purge_orig_hash net/batman-adv/network-coding.c:408 [inline]
batadv_nc_worker+0xeb/0x600 net/batman-adv/network-coding.c:719
process_one_work+0x8a2/0x1160 kernel/workqueue.c:2292
worker_thread+0xaa2/0x1270 kernel/workqueue.c:2439
kthread+0x29d/0x330 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
</TASK>
rcu: rcu_preempt kthread starved for 9844 jiffies! g34129 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x0 ->cpu=1
rcu: Unless rcu_preempt kthread gets sufficient CPU time, OOM is now expected behavior.
rcu: RCU grace-period kthread stack dump:
task:rcu_preempt state:R running task stack:27184 pid:16 ppid:2 flags:0x00004000
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5245 [inline]
__schedule+0x11d1/0x40e0 kernel/sched/core.c:6562
schedule+0xb9/0x180 kernel/sched/core.c:6638
schedule_timeout+0x184/0x2d0 kernel/time/timer.c:2168
rcu_gp_fqs_loop+0x303/0x1340 kernel/rcu/tree.c:1706
rcu_gp_kthread+0x99/0x3b0 kernel/rcu/tree.c:1905
kthread+0x29d/0x330 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
</TASK>
rcu: Stack dump where RCU GP kthread last ran:
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1 skipped: idling at native_safe_halt arch/x86/include/asm/irqflags.h:51 [inline]
NMI backtrace for cpu 1 skipped: idling at arch_safe_halt arch/x86/include/asm/irqflags.h:89 [inline]
NMI backtrace for cpu 1 skipped: idling at default_idle+0xb/0x10 arch/x86/kernel/process.c:741
sched: RT throttling activated
---
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