From: syzbot <syzbot+855b67e6ad52c740948a@syzkaller.appspotmail.com>
To: Henry.Wang@arm.com, bigeasy@linutronix.de,
linux-kernel@vger.kernel.org, longpeng2@huawei.com,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
vschneid@redhat.com
Subject: [syzbot] upstream boot error: general protection fault in rcu_core
Date: Tue, 16 Aug 2022 01:36:24 -0700 [thread overview]
Message-ID: <000000000000c0770c05e657a49b@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 5d6a0f4da927 Merge tag 'for-linus-6.0-rc1b-tag' of git://g..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=10bc4467080000
kernel config: https://syzkaller.appspot.com/x/.config?x=f83c035536d7b2e3
dashboard link: https://syzkaller.appspot.com/bug?extid=855b67e6ad52c740948a
compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+855b67e6ad52c740948a@syzkaller.appspotmail.com
general protection fault, probably for non-canonical address 0xffff000000000000: 0000 [#1] PREEMPT SMP KASAN
KASAN: maybe wild-memory-access in range [0xfff8200000000000-0xfff8200000000007]
CPU: 1 PID: 21 Comm: ksoftirqd/1 Not tainted 5.19.0-syzkaller-14374-g5d6a0f4da927 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/22/2022
RIP: 0010:rcu_do_batch kernel/rcu/tree.c:2245 [inline]
RIP: 0010:rcu_core+0xa5e/0x1710 kernel/rcu/tree.c:2505
Code: 22 69 00 4d 8b 3c 24 48 b8 00 00 00 00 00 fc ff df 80 3c 03 00 74 08 4c 89 e7 e8 6d 22 69 00 49 c7 46 08 00 00 00 00 4c 89 f7 <41> ff d7 48 c7 c7 60 08 d2 8c e8 e3 0c 00 00 65 8b 05 64 5f 8e 7e
RSP: 0000:ffffc900001b7aa0 EFLAGS: 00010246
RAX: dffffc0000000000 RBX: 1ffff11004137a06 RCX: ffff888012eb27f0
RDX: dffffc0000000000 RSI: ffffffff8aad87c0 RDI: ffff8880209bd028
RBP: ffffc900001b7cb0 R08: dffffc0000000000 R09: fffffbfff1ff3a0c
R10: fffffbfff1ff3a0c R11: 1ffffffff1ff3a0b R12: ffff8880209bd030
R13: ffff888012eb1d80 R14: ffff8880209bd028 R15: ffff000000000000
FS: 0000000000000000(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 000000000ca8e000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
__do_softirq+0x382/0x793 kernel/softirq.c:571
run_ksoftirqd+0xc1/0x120 kernel/softirq.c:934
smpboot_thread_fn+0x533/0x9d0 kernel/smpboot.c:164
kthread+0x266/0x300 kernel/kthread.c:376
ret_from_fork+0x1f/0x30
</TASK>
Modules linked in:
vkms_vblank_simulate: vblank timer overrun
---[ end trace 0000000000000000 ]---
RIP: 0010:rcu_do_batch kernel/rcu/tree.c:2245 [inline]
RIP: 0010:rcu_core+0xa5e/0x1710 kernel/rcu/tree.c:2505
Code: 22 69 00 4d 8b 3c 24 48 b8 00 00 00 00 00 fc ff df 80 3c 03 00 74 08 4c 89 e7 e8 6d 22 69 00 49 c7 46 08 00 00 00 00 4c 89 f7 <41> ff d7 48 c7 c7 60 08 d2 8c e8 e3 0c 00 00 65 8b 05 64 5f 8e 7e
RSP: 0000:ffffc900001b7aa0 EFLAGS: 00010246
RAX: dffffc0000000000 RBX: 1ffff11004137a06 RCX: ffff888012eb27f0
RDX: dffffc0000000000 RSI: ffffffff8aad87c0 RDI: ffff8880209bd028
RBP: ffffc900001b7cb0 R08: dffffc0000000000 R09: fffffbfff1ff3a0c
R10: fffffbfff1ff3a0c R11: 1ffffffff1ff3a0b R12: ffff8880209bd030
R13: ffff888012eb1d80 R14: ffff8880209bd028 R15: ffff000000000000
FS: 0000000000000000(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 000000000ca8e000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
0: 22 69 00 and 0x0(%rcx),%ch
3: 4d 8b 3c 24 mov (%r12),%r15
7: 48 b8 00 00 00 00 00 movabs $0xdffffc0000000000,%rax
e: fc ff df
11: 80 3c 03 00 cmpb $0x0,(%rbx,%rax,1)
15: 74 08 je 0x1f
17: 4c 89 e7 mov %r12,%rdi
1a: e8 6d 22 69 00 callq 0x69228c
1f: 49 c7 46 08 00 00 00 movq $0x0,0x8(%r14)
26: 00
27: 4c 89 f7 mov %r14,%rdi
* 2a: 41 ff d7 callq *%r15 <-- trapping instruction
2d: 48 c7 c7 60 08 d2 8c mov $0xffffffff8cd20860,%rdi
34: e8 e3 0c 00 00 callq 0xd1c
39: 65 8b 05 64 5f 8e 7e mov %gs:0x7e8e5f64(%rip),%eax # 0x7e8e5fa4
---
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:[~2022-08-16 10:37 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=000000000000c0770c05e657a49b@google.com \
--to=syzbot+855b67e6ad52c740948a@syzkaller.appspotmail.com \
--cc=Henry.Wang@arm.com \
--cc=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=longpeng2@huawei.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=vschneid@redhat.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 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.