[v6.1] INFO: rcu detected stall in __tun_chr_ioctl (2)

0 views
Skip to first unread message

syzbot

unread,
Mar 28, 2026, 2:58:29 PM (yesterday) Mar 28
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 1989cd3d56e2 Linux 6.1.167
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=16b3d01f980000
kernel config: https://syzkaller.appspot.com/x/.config?x=f0605c5af04d7603
dashboard link: https://syzkaller.appspot.com/bug?extid=d77d02a11256ce87187c
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/3e0cf5574b81/disk-1989cd3d.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/0c1152de55b1/vmlinux-1989cd3d.xz
kernel image: https://storage.googleapis.com/syzbot-assets/3fe87e3166b1/bzImage-1989cd3d.xz

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

rcu: INFO: rcu_preempt detected expedited stalls on CPUs/tasks: { 1-.... } 2661 jiffies s: 36149 root: 0x2/.
rcu: blocking rcu_node structures (internal RCU debug):
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 13842 Comm: syz.4.2851 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2026
RIP: 0010:pvclock_clocksource_read+0x7/0x760 arch/x86/kernel/pvclock.c:68
Code: 8b 7c 24 08 e9 f3 fe ff ff 22 05 8c 11 e7 0c 48 83 c4 18 5b 41 5c 41 5d 41 5e 41 5f 5d c3 0f 1f 44 00 00 55 41 57 41 56 41 55 <41> 54 53 48 81 ec a0 00 00 00 4c 8d 47 08 4c 8d 4f 18 48 8d 77 1c
RSP: 0018:ffffc900001e0390 EFLAGS: 00000002
RAX: f3f3f3f8f1f1f1f1 RBX: ffffc900001e0400 RCX: 152367306e2e6c00
RDX: 0000000000000000 RSI: ffffffff8adf0d00 RDI: ffffffff8fa0c040
RBP: ffffc900001e0478 R08: ffffffff8e1fdeef R09: 1ffffffff1c3fbdd
R10: dffffc0000000000 R11: fffffbfff1c3fbde R12: dffffc0000000000
R13: dffffc0000000000 R14: 1ffff9200003c07c R15: ffffffff8c651988
FS: 00007f212c52b6c0(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f92f714da08 CR3: 000000002f8fc000 CR4: 00000000003506e0
DR0: 0000200000000300 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000600
Call Trace:
<IRQ>
kvm_clock_read arch/x86/kernel/kvmclock.c:79 [inline]
kvm_sched_clock_read+0x14/0x40 arch/x86/kernel/kvmclock.c:91
sched_clock_cpu+0x6e/0x260 kernel/sched/clock.c:369
irqtime_account_irq+0x6a/0x1b0 kernel/sched/cputime.c:60
instr_sysvec_irq_work arch/x86/kernel/irq_work.c:17 [inline]
sysvec_irq_work+0x45/0xc0 arch/x86/kernel/irq_work.c:17
asm_sysvec_irq_work+0x16/0x20 arch/x86/include/asm/idtentry.h:728
RIP: 0010:rcu_read_unlock_special+0x7f/0x510 kernel/rcu/tree_plugin.h:685
Code: eb 03 48 b8 f1 f1 f1 f1 f8 f2 f2 f2 4a 89 04 2b 42 c7 44 2b 08 f8 f3 f3 f3 65 44 8b 35 d2 33 95 7e 41 f7 c6 00 00 f0 00 74 40 <48> c7 44 24 40 0e 36 e0 45 4a c7 04 2b 00 00 00 00 42 c7 44 2b 08
RSP: 0018:ffffc900001e0580 EFLAGS: 00000206
RAX: 152367306e2e6c00 RBX: 1ffff9200003c0b8 RCX: 152367306e2e6c00
RDX: dffffc0000000000 RSI: ffffffff8a8c10a0 RDI: ffffffff8adf0d20
RBP: ffffc900001e0670 R08: ffffffff90af724f R09: 1ffffffff215ee49
R10: dffffc0000000000 R11: fffffbfff215ee4a R12: 0000000000000246
R13: dffffc0000000000 R14: ffff8880b8f3b900 R15: 0000000000000002
__rcu_read_unlock+0x78/0xd0 kernel/rcu/tree_plugin.h:426
rcu_read_unlock include/linux/rcupdate.h:823 [inline]
is_bpf_text_address+0x27a/0x2a0 kernel/bpf/core.c:737
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
rcu_do_batch kernel/rcu/tree.c:2297 [inline]
rcu_core+0xa99/0x1740 kernel/rcu/tree.c:2557
handle_softirqs+0x2a1/0x930 kernel/softirq.c:596
__do_softirq kernel/softirq.c:630 [inline]
invoke_softirq kernel/softirq.c:470 [inline]
__irq_exit_rcu+0x13b/0x230 kernel/softirq.c:679
irq_exit_rcu+0x5/0x20 kernel/softirq.c:691
instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1118 [inline]
sysvec_apic_timer_interrupt+0xa0/0xc0 arch/x86/kernel/apic/apic.c:1118
</IRQ>
<TASK>
asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:691
RIP: 0010:orc_find arch/x86/kernel/unwind_orc.c:160 [inline]
RIP: 0010:unwind_next_frame+0x194/0x20b0 arch/x86/kernel/unwind_orc.c:448
Code: 6f 02 00 00 48 81 fd 00 00 00 81 0f 92 c0 48 81 fd 08 77 60 8a 0f 93 c1 08 c1 0f 85 d6 00 00 00 48 c7 c0 00 00 00 81 49 89 ee <49> 29 c6 49 c1 ee 08 8b 35 df 04 2c 0b 8d 46 ff 44 39 f0 0f 86 f4
RSP: 0018:ffffc90003b07130 EFLAGS: 00000246
RAX: ffffffff81000000 RBX: ffffc90003b07208 RCX: ffffffff96bfe100
RDX: dffffc0000000000 RSI: ffffffff82083ec5 RDI: ffffffff81391adf
RBP: ffffffff82083ec4 R08: ffffc90003b072d0 R09: 0000000000000009
R10: dffffc0000000000 R11: fffff52000760e4d R12: ffffffff8a898600
R13: dffffc0000000000 R14: ffffffff82083ec4 R15: ffffc90003b07250
arch_stack_walk+0x10c/0x140 arch/x86/kernel/stacktrace.c:25
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_slab_alloc+0x6b/0x80 mm/kasan/common.c:329
kasan_slab_alloc include/linux/kasan.h:201 [inline]
slab_post_alloc_hook+0x4b/0x480 mm/slab.h:737
slab_alloc_node mm/slub.c:3359 [inline]
slab_alloc mm/slub.c:3367 [inline]
__kmem_cache_alloc_lru mm/slub.c:3374 [inline]
kmem_cache_alloc+0x123/0x2f0 mm/slub.c:3383
kmem_cache_zalloc include/linux/slab.h:689 [inline]
__kernfs_new_node+0xe1/0x810 fs/kernfs/dir.c:614
kernfs_new_node+0x148/0x250 fs/kernfs/dir.c:690
__kernfs_create_file+0x47/0x2e0 fs/kernfs/file.c:1068
sysfs_add_file_mode_ns+0x234/0x2f0 fs/sysfs/file.c:294
create_files fs/sysfs/group.c:64 [inline]
internal_create_group+0x493/0xcf0 fs/sysfs/group.c:148
internal_create_groups fs/sysfs/group.c:188 [inline]
sysfs_create_groups+0x55/0x120 fs/sysfs/group.c:214
device_add_groups drivers/base/core.c:2752 [inline]
device_add_attrs+0xdb/0x830 drivers/base/core.c:2900
device_add+0x64b/0xfb0 drivers/base/core.c:3648
netdev_register_kobject+0x184/0x320 net/core/net-sysfs.c:2013
register_netdevice+0x12dc/0x1b00 net/core/dev.c:10230
tun_set_iff+0x848/0xed0 drivers/net/tun.c:2851
__tun_chr_ioctl+0x781/0x1e60 drivers/net/tun.c:3114
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:870 [inline]
__se_sys_ioctl+0xfa/0x170 fs/ioctl.c:856
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:0x7f212b59c819
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:00007f212c52b028 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f212b815fa0 RCX: 00007f212b59c819
RDX: 0000200000000200 RSI: 00000000400454ca RDI: 000000000000000a
RBP: 00007f212b632c91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f212b816038 R14: 00007f212b815fa0 R15: 00007ffe9773df98
</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