[v6.1] INFO: rcu detected stall in dst_destroy

6 views
Skip to first unread message

syzbot

unread,
Jul 19, 2023, 11:38:00 PM7/19/23
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: a456e1743881 Linux 6.1.39
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=15c34301a80000
kernel config: https://syzkaller.appspot.com/x/.config?x=ab4166c71cf155ea
dashboard link: https://syzkaller.appspot.com/bug?extid=a9e82b0a4cca6b9a0a64
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/e4a94ce282ec/disk-a456e174.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/7442cb7a697f/vmlinux-a456e174.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f51a327db171/bzImage-a456e174.xz

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

rcu: INFO: rcu_preempt detected expedited stalls on CPUs/tasks: { 1-...D } 2640 jiffies s: 15025 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: 9902 Comm: syz-executor.4 Not tainted 6.1.39-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/03/2023
RIP: 0010:memory_is_nonzero mm/kasan/generic.c:101 [inline]
RIP: 0010:memory_is_poisoned_n mm/kasan/generic.c:128 [inline]
RIP: 0010:memory_is_poisoned mm/kasan/generic.c:159 [inline]
RIP: 0010:check_region_inline mm/kasan/generic.c:180 [inline]
RIP: 0010:kasan_check_range+0x5f/0x290 mm/kasan/generic.c:189
Code: eb 03 49 b8 00 00 00 00 00 fc ff df 4e 8d 0c 03 4c 8d 54 37 ff 49 c1 ea 03 49 bb 01 00 00 00 00 fc ff df 4f 8d 34 1a 4c 89 f5 <4c> 29 cd 48 83 fd 10 7f 26 48 85 ed 0f 84 3a 01 00 00 49 f7 d2 49
RSP: 0018:ffffc900001e0398 EFLAGS: 00000806
RAX: 0000000000000001 RBX: 1ffff9200003c084 RCX: ffffffff816b2ffa
RDX: 0000000000000001 RSI: 0000000000000004 RDI: ffffc900001e0420
RBP: fffff5200003c085 R08: dffffc0000000000 R09: fffff5200003c084
R10: 1ffff9200003c084 R11: dffffc0000000001 R12: ffff8880230112e8
R13: 1ffff9200003c084 R14: fffff5200003c085 R15: 1ffff1100460225e
FS: 00007f6e883dd6c0(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b33220000 CR3: 0000000078782000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<NMI>
</NMI>
<IRQ>
instrument_atomic_read_write include/linux/instrumented.h:102 [inline]
atomic_try_cmpxchg_acquire include/linux/atomic/atomic-instrumented.h:542 [inline]
queued_spin_lock include/asm-generic/qspinlock.h:111 [inline]
do_raw_spin_lock+0x14a/0x370 kernel/locking/spinlock_debug.c:115
spin_lock include/linux/spinlock.h:350 [inline]
advance_sched+0x47/0x940 net/sched/sch_taprio.c:700
__run_hrtimer kernel/time/hrtimer.c:1685 [inline]
__hrtimer_run_queues+0x5e5/0xe50 kernel/time/hrtimer.c:1749
hrtimer_interrupt+0x392/0x980 kernel/time/hrtimer.c:1811
local_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1095 [inline]
__sysvec_apic_timer_interrupt+0x156/0x580 arch/x86/kernel/apic/apic.c:1112
sysvec_apic_timer_interrupt+0x3e/0xb0 arch/x86/kernel/apic/apic.c:1106
asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:649
RIP: 0010:unwind_get_return_address+0x37/0x80 arch/x86/kernel/unwind_orc.c:323
Code: 00 00 fc ff df 48 89 f8 48 c1 e8 03 42 0f b6 04 30 84 c0 75 47 83 3b 00 74 3a 48 83 c3 48 49 89 df 49 c1 ef 03 43 80 3c 37 00 <74> 08 48 89 df e8 2f da a3 00 48 8b 3b e8 17 ab 1e 00 85 c0 74 14
RSP: 0018:ffffc900001e08a0 EFLAGS: 00000246
RAX: 0000000000000000 RBX: ffffc900001e0908 RCX: 0000000080000100
RDX: dffffc0000000000 RSI: ffffc9000a578000 RDI: ffffc900001e08c0
RBP: ffffc900001e0950 R08: ffffc9000a57f628 R09: ffffc900001e0910
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff8880772bd940
R13: ffffffff8177cc20 R14: dffffc0000000000 R15: 1ffff9200003c121
arch_stack_walk+0xf3/0x140 arch/x86/kernel/stacktrace.c:26
stack_trace_save+0x113/0x1c0 kernel/stacktrace.c:122
ref_tracker_free+0x101/0x7d0 lib/ref_tracker.c:121
netdev_tracker_free include/linux/netdevice.h:4028 [inline]
netdev_put include/linux/netdevice.h:4045 [inline]
dst_destroy+0x165/0x390 net/core/dst.c:120
rcu_do_batch kernel/rcu/tree.c:2251 [inline]
rcu_core+0xa9a/0x1790 kernel/rcu/tree.c:2511
__do_softirq+0x2e9/0xa4c kernel/softirq.c:571
invoke_softirq kernel/softirq.c:445 [inline]
__irq_exit_rcu+0x155/0x240 kernel/softirq.c:650
irq_exit_rcu+0x5/0x20 kernel/softirq.c:662
sysvec_apic_timer_interrupt+0x91/0xb0 arch/x86/kernel/apic/apic.c:1106
</IRQ>
<TASK>
asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:649
RIP: 0010:nla_reserve+0x0/0x1a0 lib/nlattr.c:936
Code: 89 de e8 83 2e 19 04 49 89 c6 48 89 c7 31 f6 48 89 da e8 23 fa 83 fd 4c 89 f0 5b 41 5e c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 <55> 41 57 41 56 41 55 41 54 53 41 89 d7 41 89 f6 49 89 fc 49 bd 00
RSP: 0018:ffffc9000a57f6e0 EFLAGS: 00000292
RAX: ffff88803eb1c120 RBX: ffff88807f755c80 RCX: 0000000000040000
RDX: 0000000000000060 RSI: 0000000000000007 RDI: ffff88807f755c80
RBP: ffffc9000a57f948 R08: ffffffff89c4cd12 R09: fffff91ffffad3cb
R10: 0000000000000000 R11: dffffc0000000001 R12: 1ffff1101024504b
R13: ffff88803eb1c120 R14: ffff888081228000 R15: ffff88803eb1c11c
rtnl_fill_stats+0x59/0x880 net/core/rtnetlink.c:1246
rtnl_fill_ifinfo+0x18aa/0x2060 net/core/rtnetlink.c:1825
rtmsg_ifinfo_build_skb+0xdc/0x180 net/core/rtnetlink.c:3921
unregister_netdevice_many+0xf96/0x1870 net/core/dev.c:10850
unregister_netdevice_queue+0x2e6/0x350 net/core/dev.c:10777
unregister_vlan_dev+0x328/0x4b0 net/8021q/vlan.c:118
vlan_ioctl_handler+0x355/0x980 net/8021q/vlan.c:628
sock_ioctl+0x53c/0x770 net/socket.c:1255
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:870 [inline]
__se_sys_ioctl+0xf1/0x160 fs/ioctl.c:856
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f6e89e7cb29
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 00 00 90 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 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f6e883dd0c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f6e89f9c390 RCX: 00007f6e89e7cb29
RDX: 0000000020000000 RSI: 0000000000008982 RDI: 000000000000000b
RBP: 00007f6e89ec847a R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000006e R14: 00007f6e89f9c390 R15: 00007fff60466358
</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 bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to change bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

syzbot

unread,
Oct 27, 2023, 11:37:14 PM10/27/23
to syzkaller...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages