[v6.6] INFO: rcu detected stall in sys_getsockopt (3)

5 views
Skip to first unread message

syzbot

unread,
Sep 25, 2026, 9:51:47 PMSep 25
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 79643295eba1 Linux 6.6.157
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11540a05580000
kernel config: https://syzkaller.appspot.com/x/.config?x=7be9809cedd6b69c
dashboard link: https://syzkaller.appspot.com/bug?extid=0865a04c6517095021b4
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14513205580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/a1af8d16581c/disk-79643295.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/66be9bddb1ec/vmlinux-79643295.xz
kernel image: https://storage.googleapis.com/syzbot-assets/0329b316645d/bzImage-79643295.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+0865a0...@syzkaller.appspotmail.com

rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
rcu: Tasks blocked on level-0 rcu_node (CPUs 0-1): P5924/1:b..l
rcu: (detected by 0, t=10503 jiffies, g=13981, q=713499 ncpus=2)
task:syz-executor state:R running task stack:21672 pid:5924 ppid:5921 flags:0x00004000
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5382 [inline]
__schedule+0x15ae/0x4660 kernel/sched/core.c:6701
preempt_schedule_irq+0xbf/0x150 kernel/sched/core.c:7011
irqentry_exit+0x67/0x70 kernel/entry/common.c:441
asm_sysvec_apic_timer_interrupt+0x1a/0x20 arch/x86/include/asm/idtentry.h:687
RIP: 0010:lock_acquire+0x208/0x420 kernel/locking/lockdep.c:5760
Code: f7 84 24 80 00 00 00 00 02 00 00 43 c6 44 3c 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 04 3c 00 00 00 00 43 c7 44 3c 08 00 00 00 00 65 48 8b 04 25
RSP: 0018:ffffc9000333f040 EFLAGS: 00000206
RAX: 0000000000000001 RBX: 0000000000000000 RCX: e6fbfe453c3ea700
RDX: 0000000000000000 RSI: ffffffff8acade60 RDI: ffffffff8b1d3ba0
RBP: ffffc9000333f150 R08: dffffc0000000000 R09: 1ffffffff223d6a0
R10: dffffc0000000000 R11: fffffbfff223d6a1 R12: 1ffff92000667e14
R13: ffffffff8d1320e0 R14: 0000000000000246 R15: dffffc0000000000
rcu_lock_acquire include/linux/rcupdate.h:334 [inline]
rcu_read_lock include/linux/rcupdate.h:786 [inline]
is_bpf_text_address+0x47/0x2a0 kernel/bpf/core.c:742
kernel_text_address+0xa0/0xd0 kernel/extable.c:125
__kernel_text_address+0xd/0x30 kernel/extable.c:79
unwind_get_return_address+0x5d/0xc0 arch/x86/kernel/unwind_orc.c:369
arch_stack_walk+0x11d/0x190 arch/x86/kernel/stacktrace.c:26
stack_trace_save+0xaa/0x100 kernel/stacktrace.c:122
kasan_save_stack mm/kasan/common.c:46 [inline]
kasan_set_track+0x4e/0x70 mm/kasan/common.c:53
____kasan_kmalloc mm/kasan/common.c:375 [inline]
__kasan_kmalloc+0x8f/0xa0 mm/kasan/common.c:384
kasan_kmalloc include/linux/kasan.h:198 [inline]
__do_kmalloc_node mm/slab_common.c:1007 [inline]
__kmalloc_node+0xb6/0x240 mm/slab_common.c:1014
kmalloc_node include/linux/slab.h:620 [inline]
__vmalloc_area_node mm/vmalloc.c:3175 [inline]
__vmalloc_node_range+0x598/0x1320 mm/vmalloc.c:3370
__vmalloc_node mm/vmalloc.c:3435 [inline]
vzalloc+0x79/0x90 mm/vmalloc.c:3508
alloc_counters+0xcb/0x6c0 net/ipv4/netfilter/ip_tables.c:799
copy_entries_to_user net/ipv6/netfilter/ip6_tables.c:837 [inline]
get_entries net/ipv6/netfilter/ip6_tables.c:1037 [inline]
do_ip6t_get_ctl+0xad5/0x1220 net/ipv6/netfilter/ip6_tables.c:1674
nf_getsockopt+0x262/0x280 net/netfilter/nf_sockopt.c:116
ipv6_getsockopt+0x233/0x2e0 net/ipv6/ipv6_sockglue.c:1499
do_sock_getsockopt+0x379/0x450 net/socket.c:2384
__sys_getsockopt net/socket.c:2413 [inline]
__do_sys_getsockopt net/socket.c:2423 [inline]
__se_sys_getsockopt net/socket.c:2420 [inline]
__x64_sys_getsockopt+0x1d6/0x280 net/socket.c:2420
do_syscall_x64 arch/x86/entry/common.c:46 [inline]
do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:76
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f7b1499f92a
RSP: 002b:00007ffc70f9e988 EFLAGS: 00000212 ORIG_RAX: 0000000000000037
RAX: ffffffffffffffda RBX: 00007ffc70f9ea10 RCX: 00007f7b1499f92a
RDX: 0000000000000041 RSI: 0000000000000029 RDI: 0000000000000003
RBP: 0000000000000003 R08: 00007ffc70f9e9ac R09: 0000000000000000
R10: 00007ffc70f9ea10 R11: 0000000000000212 R12: 00007f7b14bef900
R13: 00007ffc70f9e9ac R14: 0000000000000000 R15: 00007f7b14beffc0
</TASK>
rcu: rcu_preempt kthread starved for 10561 jiffies! g13981 f0x2 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:26856 pid:17 ppid:2 flags:0x00004000
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5382 [inline]
__schedule+0x15ae/0x4660 kernel/sched/core.c:6701
schedule+0xbd/0x170 kernel/sched/core.c:6775
schedule_timeout+0x188/0x2d0 kernel/time/timer.c:2168
rcu_gp_fqs_loop+0x30d/0x1590 kernel/rcu/tree.c:1667
rcu_gp_kthread+0x9d/0x3b0 kernel/rcu/tree.c:1866
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>
rcu: Stack dump where RCU GP kthread last ran:
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 6596 Comm: syz.2.302 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
RIP: 0010:__sanitizer_cov_trace_switch+0x3a/0xe0 kernel/kcov.c:-1
Code: 31 ca 48 39 ca 0f 86 c3 00 00 00 f3 48 0f bc c8 48 83 c1 fd 48 83 f9 03 0f 87 b0 00 00 00 48 8b 06 48 85 c0 0f 84 a4 00 00 00 <41> 57 41 56 41 54 53 48 8d 4c 09 01 48 8b 54 24 20 65 4c 8b 05 9d
RSP: 0018:ffffc9000c50f850 EFLAGS: 00000206
RAX: 0000000000000003 RBX: ffffffff8f1cdc73 RCX: 0000000000000001
RDX: 000000000000001f RSI: ffffffff8cfa0950 RDI: 0000000000000002
RBP: ffffc9000c50fde0 R08: ffff88802b833c00 R09: 0000000000000008
R10: 0000000000000009 R11: 0000000000000000 R12: ffffffff8f1cdc72
R13: ffffc9000c50f928 R14: 0000000000000002 R15: dffffc0000000000
FS: 00007f3b3113a6c0(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000200000001840 CR3: 00000000316b3000 CR4: 00000000003506e0
Call Trace:
<TASK>
unwind_next_frame+0xe42/0x2990 arch/x86/kernel/unwind_orc.c:581
arch_stack_walk+0x144/0x190 arch/x86/kernel/stacktrace.c:25
stack_trace_save+0xaa/0x100 kernel/stacktrace.c:122
kasan_save_stack mm/kasan/common.c:46 [inline]
kasan_set_track+0x4e/0x70 mm/kasan/common.c:53
__kasan_slab_alloc+0x6c/0x80 mm/kasan/common.c:329
kasan_slab_alloc include/linux/kasan.h:188 [inline]
slab_post_alloc_hook+0x6a/0x4d0 mm/slab.h:770
slab_alloc_node mm/slub.c:3495 [inline]
slab_alloc mm/slub.c:3503 [inline]
__kmem_cache_alloc_lru mm/slub.c:3510 [inline]
kmem_cache_alloc+0x17e/0x2c0 mm/slub.c:3519
getname_flags+0xbb/0x500 fs/namei.c:140
do_sys_openat2+0xda/0x1d0 fs/open.c:1416
do_sys_open fs/open.c:1437 [inline]
__do_sys_openat fs/open.c:1453 [inline]
__se_sys_openat fs/open.c:1448 [inline]
__x64_sys_openat+0x139/0x160 fs/open.c:1448
do_syscall_x64 arch/x86/entry/common.c:46 [inline]
do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:76
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f3b3019e159
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f3b3113a028 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00007f3b30425fa0 RCX: 00007f3b3019e159
RDX: 0000000000002982 RSI: 0000200000001840 RDI: ffffffffffffff9c
RBP: 00007f3b3023506b R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f3b30426038 R14: 00007f3b30425fa0 R15: 00007ffe49e55a98
</TASK>
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 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