From: syzbot <syzbot+735579fbeb0c09a90cfa@syzkaller.appspotmail.com>
To: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
pbonzini@redhat.com, syzkaller-bugs@googlegroups.com
Subject: WARNING in cleanup_srcu_struct (2)
Date: Mon, 21 Sep 2020 02:02:21 -0700 [thread overview]
Message-ID: <000000000000b4ac9e05afcf1b13@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 5925fa68 Merge tag 'perf-tools-fixes-for-v5.9-2020-09-16' ..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14b72f01900000
kernel config: https://syzkaller.appspot.com/x/.config?x=c61f6bd349c981f3
dashboard link: https://syzkaller.appspot.com/bug?extid=735579fbeb0c09a90cfa
compiler: gcc (GCC) 10.1.0-syz 20200507
Unfortunately, I don't have any reproducer for this issue yet.
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+735579fbeb0c09a90cfa@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 1 PID: 14586 at kernel/rcu/srcutree.c:389 cleanup_srcu_struct+0x23b/0x2d0 kernel/rcu/srcutree.c:408
Kernel panic - not syncing: panic_on_warn set ...
CPU: 1 PID: 14586 Comm: syz-executor.5 Not tainted 5.9.0-rc5-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x198/0x1fd lib/dump_stack.c:118
panic+0x347/0x7c0 kernel/panic.c:231
__warn.cold+0x20/0x46 kernel/panic.c:600
report_bug+0x1bd/0x210 lib/bug.c:198
handle_bug+0x38/0x90 arch/x86/kernel/traps.c:234
exc_invalid_op+0x14/0x40 arch/x86/kernel/traps.c:254
asm_exc_invalid_op+0x12/0x20 arch/x86/include/asm/idtentry.h:536
RIP: 0010:cleanup_srcu_struct+0x23b/0x2d0 kernel/rcu/srcutree.c:389
Code: 84 24 98 04 00 00 00 00 00 00 48 83 c4 18 5b 5d 41 5c 41 5d 41 5e 41 5f c3 0f 0b 48 83 c4 18 5b 5d 41 5c 41 5d 41 5e 41 5f c3 <0f> 0b e9 36 ff ff ff 48 8b 3c 24 e8 45 88 53 00 e9 b7 fe ff ff 48
RSP: 0018:ffffc90018f27a18 EFLAGS: 00010202
RAX: 0000000000000001 RBX: 0000000000000000 RCX: ffffffff839a9211
RDX: ffff88804f2de100 RSI: ffffffff839a92c3 RDI: 0000000000000006
RBP: 0000000000000001 R08: 0000000000000040 R09: 0000000000000001
R10: 0000000000000040 R11: 0000000000000000 R12: ffffc900057b3020
R13: ffffc900057a9000 R14: ffff88806cfbf000 R15: ffffc900057b2840
kvm_destroy_vm+0x777/0xbe0 arch/x86/kvm/../../../virt/kvm/kvm_main.c:882
kvm_put_kvm arch/x86/kvm/../../../virt/kvm/kvm_main.c:899 [inline]
kvm_vm_release+0xac/0xe0 arch/x86/kvm/../../../virt/kvm/kvm_main.c:922
__fput+0x285/0x920 fs/file_table.c:281
task_work_run+0xdd/0x190 kernel/task_work.c:141
exit_task_work include/linux/task_work.h:25 [inline]
do_exit+0xb7d/0x29f0 kernel/exit.c:806
do_group_exit+0x125/0x310 kernel/exit.c:903
get_signal+0x428/0x1f00 kernel/signal.c:2757
arch_do_signal+0x82/0x2520 arch/x86/kernel/signal.c:811
exit_to_user_mode_loop kernel/entry/common.c:159 [inline]
exit_to_user_mode_prepare+0x1ae/0x200 kernel/entry/common.c:190
irqentry_exit_to_user_mode+0x5/0x30 kernel/entry/common.c:278
asm_common_interrupt+0x1e/0x40 arch/x86/include/asm/idtentry.h:572
RIP: 0033:0x41221c
Code: Bad RIP value.
RSP: 002b:00007ffe0eb2c660 EFLAGS: 00000202
RAX: 0000000036b92991 RBX: 000000003787d99d RCX: 0000001b2da20000
RDX: 0000000036b92991 RSI: 0000000000000991 RDI: ffffffff36b92991
RBP: 0000000000001914 R08: 0000000036b92991 R09: 0000000036b92995
R10: 00007ffe0eb2c7d0 R11: 0000000000000246 R12: 000000000118cfc8
R13: 00007fb1a8045008 R14: 00007fb1a8045000 R15: 000000000003ce98
Kernel Offset: disabled
Rebooting in 86400 seconds..
---
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 syzkaller@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
reply other threads:[~2020-09-21 9:02 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=000000000000b4ac9e05afcf1b13@google.com \
--to=syzbot+735579fbeb0c09a90cfa@syzkaller.appspotmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=syzkaller-bugs@googlegroups.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®