INFO: rcu detected stall in garp_join_timer

9 views
Skip to first unread message

syzbot

unread,
Jan 8, 2020, 2:29:10 AM1/8/20
to syzkaller...@googlegroups.com
Hello,

syzbot found the following crash on:

HEAD commit: 3d40d711 Linux 4.19.93
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1421deb9e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=be639726c8387103
dashboard link: https://syzkaller.appspot.com/bug?extid=bd714e8a7cb90f3f553a
compiler: gcc (GCC) 9.0.0 20181231 (experimental)

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

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

nla_parse: 2 callbacks suppressed
netlink: 20 bytes leftover after parsing attributes in process
`syz-executor.0'.
rcu: INFO: rcu_preempt self-detected stall on CPU
rcu: 0-....: (1 GPs behind) idle=da6/1/0x4000000000000004
softirq=216615/216616 fqs=5248
rcu: (t=10502 jiffies g=272981 q=1701)
NMI backtrace for cpu 0
CPU: 0 PID: 2667 Comm: syz-executor.2 Not tainted 4.19.93-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
Call Trace:
<IRQ>
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x197/0x210 lib/dump_stack.c:118
nmi_cpu_backtrace.cold+0x63/0xa4 lib/nmi_backtrace.c:101
nmi_trigger_cpumask_backtrace+0x1b0/0x1f8 lib/nmi_backtrace.c:62
arch_trigger_cpumask_backtrace+0x14/0x20 arch/x86/kernel/apic/hw_nmi.c:38
trigger_single_cpu_backtrace include/linux/nmi.h:164 [inline]
rcu_dump_cpu_stacks+0x189/0x1d5 kernel/rcu/tree.c:1340
print_cpu_stall kernel/rcu/tree.c:1478 [inline]
check_cpu_stall kernel/rcu/tree.c:1550 [inline]
__rcu_pending kernel/rcu/tree.c:3293 [inline]
rcu_pending kernel/rcu/tree.c:3336 [inline]
rcu_check_callbacks.cold+0x5e3/0xd90 kernel/rcu/tree.c:2682
update_process_times+0x32/0x80 kernel/time/timer.c:1638
tick_sched_handle+0xa2/0x190 kernel/time/tick-sched.c:164
tick_sched_timer+0x47/0x130 kernel/time/tick-sched.c:1274
__run_hrtimer kernel/time/hrtimer.c:1401 [inline]
__hrtimer_run_queues+0x33b/0xdc0 kernel/time/hrtimer.c:1463
hrtimer_interrupt+0x314/0x770 kernel/time/hrtimer.c:1521
local_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1067 [inline]
smp_apic_timer_interrupt+0x111/0x550 arch/x86/kernel/apic/apic.c:1092
apic_timer_interrupt+0xf/0x20 arch/x86/entry/entry_64.S:893
RIP: 0010:arch_local_irq_restore arch/x86/include/asm/paravirt.h:789
[inline]
RIP: 0010:__raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:160
[inline]
RIP: 0010:_raw_spin_unlock_irqrestore+0x95/0xe0
kernel/locking/spinlock.c:184
Code: 48 c7 c0 c8 5b f2 88 48 ba 00 00 00 00 00 fc ff df 48 c1 e8 03 80 3c
10 00 75 39 48 83 3d fa 8b 9c 01 00 74 24 48 89 df 57 9d <0f> 1f 44 00 00
bf 01 00 00 00 e8 ec 3f f3 f9 65 8b 05 e5 1d ac 78
RSP: 0018:ffff8880ae807bc8 EFLAGS: 00000282 ORIG_RAX: ffffffffffffff13
RAX: 1ffffffff11e4b79 RBX: 0000000000000282 RCX: 1ffff11002a5dd51
RDX: dffffc0000000000 RSI: ffff8880152eea68 RDI: 0000000000000282
RBP: ffff8880ae807bd8 R08: ffff8880152ee1c0 R09: ffff8880152eea88
R10: 0000000000000000 R11: 0000000000000000 R12: ffff8880ae823a00
R13: 0000000000000000 R14: 0000000000000000 R15: ffff8880ae823a00
__mod_timer kernel/time/timer.c:1059 [inline]
mod_timer+0x571/0x1030 kernel/time/timer.c:1102
garp_join_timer_arm+0x5e/0x80 net/802/garp.c:401
garp_join_timer+0x73/0x80 net/802/garp.c:414
call_timer_fn+0x18d/0x720 kernel/time/timer.c:1326
expire_timers kernel/time/timer.c:1363 [inline]
__run_timers kernel/time/timer.c:1684 [inline]
__run_timers kernel/time/timer.c:1652 [inline]
run_timer_softirq+0x64f/0x16a0 kernel/time/timer.c:1697
__do_softirq+0x25c/0x921 kernel/softirq.c:292
invoke_softirq kernel/softirq.c:372 [inline]
irq_exit+0x180/0x1d0 kernel/softirq.c:412
exiting_irq arch/x86/include/asm/apic.h:536 [inline]
smp_apic_timer_interrupt+0x13b/0x550 arch/x86/kernel/apic/apic.c:1094
apic_timer_interrupt+0xf/0x20 arch/x86/entry/entry_64.S:893
</IRQ>
RIP: 0010:sidtab_search_cache security/selinux/ss/sidtab.c:179 [inline]
RIP: 0010:sidtab_context_to_sid+0x149/0x11e0
security/selinux/ss/sidtab.c:201
Code: 44 89 f6 e8 19 6b 42 fe 45 85 f6 0f 85 88 0b 00 00 e8 8b 69 42 fe 83
c3 01 bf 03 00 00 00 89 de e8 fc 6a 42 fe 48 83 45 c8 08 <83> fb 03 0f 85
35 ff ff ff 49 bd 00 00 00 00 00 fc ff df 48 8b 45
RSP: 0018:ffff88800c227a50 EFLAGS: 00000296 ORIG_RAX: ffffffffffffff13
RAX: 0000000000000002 RBX: 0000000000000001 RCX: ffffffff8328db54
RDX: 0000000000000001 RSI: 0000000000000003 RDI: 0000000000000005
RBP: ffff88800c227ae0 R08: ffff8880152ee1c0 R09: ffffed1011908e37
R10: ffffed1011908e36 R11: ffff88808c8471b7 R12: ffff88809894ca80
R13: dffffc0000000000 R14: 0000000500000006 R15: ffff88800c227be8
security_compute_sid.part.0+0xb53/0x15c0
security/selinux/ss/services.c:1800
security_compute_sid security/selinux/ss/services.c:1825 [inline]
security_transition_sid+0x126/0x190 security/selinux/ss/services.c:1825
socket_sockcreate_sid security/selinux/hooks.c:4558 [inline]
socket_sockcreate_sid security/selinux/hooks.c:4550 [inline]
selinux_socket_create+0x44c/0x610 security/selinux/hooks.c:4592
security_socket_create+0x7b/0xc0 security/security.c:1379
__sock_create+0x90/0x730 net/socket.c:1231
sock_create net/socket.c:1316 [inline]
__sys_socket+0x103/0x220 net/socket.c:1346
__do_sys_socket net/socket.c:1355 [inline]
__se_sys_socket net/socket.c:1353 [inline]
__x64_sys_socket+0x73/0xb0 net/socket.c:1353
do_syscall_64+0xfd/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x45af49
Code: ad b6 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 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 0f 83 7b b6 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007fd49c32cc78 EFLAGS: 00000246 ORIG_RAX: 0000000000000029
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 000000000045af49
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 000000000000000a
RBP: 000000000075bf20 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007fd49c32d6d4
R13: 00000000004cb84c R14: 00000000004e6030 R15: 00000000ffffffff
rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
rcu: 0-....: (10583 ticks this GP) idle=da6/1/0x4000000000000002
softirq=216567/216616 fqs=5223
rcu: (detected by 1, t=10502 jiffies, g=49809, q=1)
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 2667 Comm: syz-executor.2 Not tainted 4.19.93-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
RIP: 0010:cpu_max_bits_warn include/linux/cpumask.h:121 [inline]
RIP: 0010:cpumask_check include/linux/cpumask.h:128 [inline]
RIP: 0010:cpumask_test_cpu include/linux/cpumask.h:344 [inline]
RIP: 0010:trace_lock_acquire include/trace/events/lock.h:13 [inline]
RIP: 0010:lock_acquire+0x128/0x3f0 kernel/locking/lockdep.c:3902
Code: 89 f8 83 e0 07 83 c0 03 38 d0 7c 08 84 d2 0f 85 25 02 00 00 c7 83 7c
08 00 00 01 00 00 00 0f 1f 44 00 00 65 8b 05 58 03 af 7e <83> f8 3f 0f 87
ed 01 00 00 89 c0 48 0f a3 05 75 99 7b 08 0f 82 98
RSP: 0018:ffff8880ae8079b8 EFLAGS: 00000046
RAX: 0000000000000000 RBX: ffff8880152ee1c0 RCX: 0000000000000000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff8880152eea3c
RBP: ffff8880ae807a00 R08: 0000000000000001 R09: 0000000000000000
R10: ffffed1015d04732 R11: 0000000000000001 R12: ffff8880ae825b98
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
FS: 00007fd49c32d700(0000) GS:ffff8880ae800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000738000 CR3: 0000000018f88000 CR4: 00000000001406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<IRQ>
__raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]
_raw_spin_lock_irqsave+0x95/0xcd kernel/locking/spinlock.c:152
hrtimer_interrupt+0xff/0x770 kernel/time/hrtimer.c:1502
local_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1067 [inline]
smp_apic_timer_interrupt+0x111/0x550 arch/x86/kernel/apic/apic.c:1092
apic_timer_interrupt+0xf/0x20 arch/x86/entry/entry_64.S:893
RIP: 0010:arch_local_irq_restore arch/x86/include/asm/paravirt.h:789
[inline]
RIP: 0010:__raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:160
[inline]
RIP: 0010:_raw_spin_unlock_irqrestore+0x95/0xe0
kernel/locking/spinlock.c:184
Code: 48 c7 c0 c8 5b f2 88 48 ba 00 00 00 00 00 fc ff df 48 c1 e8 03 80 3c
10 00 75 39 48 83 3d fa 8b 9c 01 00 74 24 48 89 df 57 9d <0f> 1f 44 00 00
bf 01 00 00 00 e8 ec 3f f3 f9 65 8b 05 e5 1d ac 78
RSP: 0018:ffff8880ae807bd8 EFLAGS: 00000282 ORIG_RAX: ffffffffffffff13
RAX: 1ffffffff11e4b79 RBX: 0000000000000282 RCX: 1ffff11002a5dd51
RDX: dffffc0000000000 RSI: ffff8880152eea68 RDI: 0000000000000282
RBP: ffff8880ae807be8 R08: ffff8880152ee1c0 R09: ffff8880152eea88
R10: 0000000000000000 R11: 0000000000000000 R12: ffff8880ae823a00
R13: 0000000000000000 R14: 0000000000000000 R15: ffff8880ae823a00
__mod_timer kernel/time/timer.c:1059 [inline]
mod_timer+0x571/0x1030 kernel/time/timer.c:1102
mrp_periodic_timer_arm+0x4a/0x70 net/802/mrp.c:604
mrp_periodic_timer+0x46/0x50 net/802/mrp.c:617
call_timer_fn+0x18d/0x720 kernel/time/timer.c:1326
expire_timers kernel/time/timer.c:1363 [inline]
__run_timers kernel/time/timer.c:1684 [inline]
__run_timers kernel/time/timer.c:1652 [inline]
run_timer_softirq+0x64f/0x16a0 kernel/time/timer.c:1697
__do_softirq+0x25c/0x921 kernel/softirq.c:292
invoke_softirq kernel/softirq.c:372 [inline]
irq_exit+0x180/0x1d0 kernel/softirq.c:412
exiting_irq arch/x86/include/asm/apic.h:536 [inline]
smp_apic_timer_interrupt+0x13b/0x550 arch/x86/kernel/apic/apic.c:1094
apic_timer_interrupt+0xf/0x20 arch/x86/entry/entry_64.S:893
</IRQ>
RIP: 0010:sidtab_search_cache security/selinux/ss/sidtab.c:179 [inline]
RIP: 0010:sidtab_context_to_sid+0x149/0x11e0
security/selinux/ss/sidtab.c:201
Code: 44 89 f6 e8 19 6b 42 fe 45 85 f6 0f 85 88 0b 00 00 e8 8b 69 42 fe 83
c3 01 bf 03 00 00 00 89 de e8 fc 6a 42 fe 48 83 45 c8 08 <83> fb 03 0f 85
35 ff ff ff 49 bd 00 00 00 00 00 fc ff df 48 8b 45
RSP: 0018:ffff88800c227a50 EFLAGS: 00000296 ORIG_RAX: ffffffffffffff13
RAX: 0000000000000002 RBX: 0000000000000001 RCX: ffffffff8328db54
RDX: 0000000000000001 RSI: 0000000000000003 RDI: 0000000000000005
RBP: ffff88800c227ae0 R08: ffff8880152ee1c0 R09: ffffed1011908e37
R10: ffffed1011908e36 R11: ffff88808c8471b7 R12: ffff88809894ca80
R13: dffffc0000000000 R14: 0000000500000006 R15: ffff88800c227be8
security_compute_sid.part.0+0xb53/0x15c0
security/selinux/ss/services.c:1800
security_compute_sid security/selinux/ss/services.c:1825 [inline]
security_transition_sid+0x126/0x190 security/selinux/ss/services.c:1825
socket_sockcreate_sid security/selinux/hooks.c:4558 [inline]
socket_sockcreate_sid security/selinux/hooks.c:4550 [inline]
selinux_socket_create+0x44c/0x610 security/selinux/hooks.c:4592
security_socket_create+0x7b/0xc0 security/security.c:1379
__sock_create+0x90/0x730 net/socket.c:1231
sock_create net/socket.c:1316 [inline]
__sys_socket+0x103/0x220 net/socket.c:1346
__do_sys_socket net/socket.c:1355 [inline]
__se_sys_socket net/socket.c:1353 [inline]
__x64_sys_socket+0x73/0xb0 net/socket.c:1353
do_syscall_64+0xfd/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x45af49
Code: ad b6 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 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 0f 83 7b b6 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007fd49c32cc78 EFLAGS: 00000246 ORIG_RAX: 0000000000000029
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 000000000045af49
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 000000000000000a
RBP: 000000000075bf20 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007fd49c32d6d4
R13: 00000000004cb84c R14: 00000000004e6030 R15: 00000000ffffffff


---
This bug 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 bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

syzbot

unread,
Jun 7, 2020, 9:30:11 AM6/7/20
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