From: syzbot <syzbot+1ffacdc3e8cc60303b4e@syzkaller.appspotmail.com>
To: fweisbec@gmail.com, linux-kernel@vger.kernel.org,
mingo@kernel.org, syzkaller-bugs@googlegroups.com,
tglx@linutronix.de
Subject: INFO: rcu detected stall in pfkey_sendmsg (2)
Date: Tue, 14 Jul 2020 03:53:19 -0700 [thread overview]
Message-ID: <00000000000081412705aa649deb@google.com> (raw)
Hello,
syzbot found the following crash on:
HEAD commit: be978f8f Add linux-next specific files for 20200713
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=13c5468b100000
kernel config: https://syzkaller.appspot.com/x/.config?x=f90bd54d8a9a6104
dashboard link: https://syzkaller.appspot.com/bug?extid=1ffacdc3e8cc60303b4e
compiler: gcc (GCC) 10.1.0-syz 20200507
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+1ffacdc3e8cc60303b4e@syzkaller.appspotmail.com
rcu: INFO: rcu_preempt self-detected stall on CPU
rcu: 1-....: (1 GPs behind) idle=84a/1/0x4000000000000000 softirq=24372/24373 fqs=5236
(t=10502 jiffies g=37585 q=10697)
NMI backtrace for cpu 1
CPU: 1 PID: 13505 Comm: syz-executor.0 Not tainted 5.8.0-rc4-next-20200713-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+0x18f/0x20d lib/dump_stack.c:118
nmi_cpu_backtrace.cold+0x44/0xd7 lib/nmi_backtrace.c:105
nmi_trigger_cpumask_backtrace+0x1b3/0x223 lib/nmi_backtrace.c:62
trigger_single_cpu_backtrace include/linux/nmi.h:165 [inline]
rcu_dump_cpu_stacks+0x194/0x1cf kernel/rcu/tree_stall.h:318
print_cpu_stall kernel/rcu/tree_stall.h:551 [inline]
check_cpu_stall kernel/rcu/tree_stall.h:625 [inline]
rcu_pending kernel/rcu/tree.c:3626 [inline]
rcu_sched_clock_irq.cold+0x5b3/0xcbd kernel/rcu/tree.c:2509
update_process_times+0x25/0x60 kernel/time/timer.c:1726
tick_sched_handle+0x9b/0x180 kernel/time/tick-sched.c:176
tick_sched_timer+0x108/0x290 kernel/time/tick-sched.c:1328
__run_hrtimer kernel/time/hrtimer.c:1520 [inline]
__hrtimer_run_queues+0x1d5/0xfc0 kernel/time/hrtimer.c:1584
hrtimer_interrupt+0x32a/0x930 kernel/time/hrtimer.c:1646
local_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1079 [inline]
__sysvec_apic_timer_interrupt+0x142/0x5e0 arch/x86/kernel/apic/apic.c:1096
asm_call_on_stack+0xf/0x20 arch/x86/entry/entry_64.S:706
</IRQ>
__run_on_irqstack arch/x86/include/asm/irq_stack.h:22 [inline]
run_on_irqstack_cond arch/x86/include/asm/irq_stack.h:48 [inline]
sysvec_apic_timer_interrupt+0xe0/0x120 arch/x86/kernel/apic/apic.c:1090
asm_sysvec_apic_timer_interrupt+0x12/0x20 arch/x86/include/asm/idtentry.h:587
RIP: 0010:ipv6_addr_equal include/net/ipv6.h:579 [inline]
RIP: 0010:xfrm6_addr_equal include/net/xfrm.h:1699 [inline]
RIP: 0010:__xfrm6_tunnel_spi_lookup+0x23f/0x3b0 net/ipv6/xfrm6_tunnel.c:82
Code: 4d 85 e4 74 53 e8 01 78 7b fa 49 8d 7c 24 20 48 89 f8 48 c1 e8 03 80 3c 28 00 0f 85 2d 01 00 00 4d 8b 7c 24 20 49 8d 7c 24 28 <48> 89 f8 48 c1 e8 03 4d 31 f7 80 3c 28 00 0f 85 05 01 00 00 49 8b
RSP: 0018:ffffc9000d5a7580 EFLAGS: 00000246
RAX: 1ffff1101347618e RBX: cc5e8ead76490000 RCX: ffffc90001db9000
RDX: 0000000000040000 RSI: ffffffff86f8b96f RDI: ffff88809a3b0c78
RBP: dffffc0000000000 R08: 0000000000000001 R09: ffff8880a86a2990
R10: 0000000000000000 R11: 0000000000000000 R12: ffff88809a3b0c50
R13: cc5e8ead06000000 R14: 0000000074490000 R15: 0000000000000000
xfrm6_tunnel_spi_lookup+0x8a/0x1d0 net/ipv6/xfrm6_tunnel.c:95
ipcomp6_tunnel_attach net/ipv6/ipcomp6.c:119 [inline]
ipcomp6_init_state net/ipv6/ipcomp6.c:159 [inline]
ipcomp6_init_state+0x1de/0x700 net/ipv6/ipcomp6.c:139
__xfrm_init_state+0x9a6/0x14b0 net/xfrm/xfrm_state.c:2498
xfrm_init_state+0x1a/0x70 net/xfrm/xfrm_state.c:2525
pfkey_msg2xfrm_state net/key/af_key.c:1291 [inline]
pfkey_add+0x1a10/0x2b70 net/key/af_key.c:1508
pfkey_process+0x66d/0x7a0 net/key/af_key.c:2834
pfkey_sendmsg+0x42d/0x800 net/key/af_key.c:3673
sock_sendmsg_nosec net/socket.c:652 [inline]
sock_sendmsg+0xcf/0x120 net/socket.c:672
____sys_sendmsg+0x331/0x810 net/socket.c:2363
___sys_sendmsg+0xf3/0x170 net/socket.c:2417
__sys_sendmmsg+0x195/0x480 net/socket.c:2507
__do_sys_sendmmsg net/socket.c:2536 [inline]
__se_sys_sendmmsg net/socket.c:2533 [inline]
__x64_sys_sendmmsg+0x99/0x100 net/socket.c:2533
do_syscall_64+0x60/0xe0 arch/x86/entry/common.c:384
entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x45cba9
Code: Bad RIP value.
RSP: 002b:00007f108b804c78 EFLAGS: 00000246 ORIG_RAX: 0000000000000133
RAX: ffffffffffffffda RBX: 00000000004fe340 RCX: 000000000045cba9
RDX: 0000000000000393 RSI: 0000000020000180 RDI: 0000000000000003
RBP: 000000000078bf00 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00000000ffffffff
R13: 0000000000000919 R14: 00000000004cbed9 R15: 00007f108b8056d4
---
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 syzkaller@googlegroups.com.
syzbot will keep track of this bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
reply other threads:[~2020-07-14 10:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=00000000000081412705aa649deb@google.com \
--to=syzbot+1ffacdc3e8cc60303b4e@syzkaller.appspotmail.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.