From: syzbot <syzbot+95ea0d29692df9761488@syzkaller.appspotmail.com>
To: bp@alien8.de, dave.hansen@linux.intel.com, hpa@zytor.com,
linux-kernel@vger.kernel.org, linux-next@vger.kernel.org,
masahiroy@kernel.org, mingo@redhat.com, nathan@kernel.org,
peterz@infradead.org, sfr@canb.auug.org.au,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
x86@kernel.org
Subject: [syzbot] linux-next boot error: general protection fault in __switch_to
Date: Wed, 10 Aug 2022 02:13:23 -0700 [thread overview]
Message-ID: <000000000000fe1d6705e5df7580@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: bc6c6584ffb2 Add linux-next specific files for 20220810
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=13f5fcd1080000
kernel config: https://syzkaller.appspot.com/x/.config?x=5784be4315a4403b
dashboard link: https://syzkaller.appspot.com/bug?extid=95ea0d29692df9761488
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, 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+95ea0d29692df9761488@syzkaller.appspotmail.com
general protection fault, maybe for address 0xffff888020655880: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 1089 Comm: kworker/u4:4 Not tainted 5.19.0-next-20220810-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/22/2022
RIP: 0010:__switch_to+0x680/0x1050 arch/x86/kernel/process_64.c:661
Code: 67 05 00 00 eb 13 0f 1f 00 66 8c d0 66 83 f8 18 74 07 b8 18 00 00 00 8e d0 48 83 c4 10 4c 89 e0 5b 5d 41 5c 41 5d 41 5e 41 5f <c3> 48 8d bd 28 18 00 00 48 b8 00 00 00 00 00 fc ff df 48 89 fa 48
RSP: 0000:ffffc900057cf530 EFLAGS: 00010086
RAX: ffff888020655880 RBX: ffff000000000000 RCX: ffffffff812a921c
RDX: 1ffff110040cab10 RSI: 0000000000000008 RDI: ffff888020523b00
RBP: ffff000000000000 R08: 0000000000000001 R09: ffff888020523b07
R10: ffffed10040a4760 R11: 0000000000000000 R12: ffff000000000000
R13: ffff000000000000 R14: ffff000000000000 R15: ffff000000000000
FS: 0000000000000000(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 000000000bc8e000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:__switch_to+0x680/0x1050 arch/x86/kernel/process_64.c:661
Code: 67 05 00 00 eb 13 0f 1f 00 66 8c d0 66 83 f8 18 74 07 b8 18 00 00 00 8e d0 48 83 c4 10 4c 89 e0 5b 5d 41 5c 41 5d 41 5e 41 5f <c3> 48 8d bd 28 18 00 00 48 b8 00 00 00 00 00 fc ff df 48 89 fa 48
RSP: 0000:ffffc900057cf530 EFLAGS: 00010086
RAX: ffff888020655880 RBX: ffff000000000000 RCX: ffffffff812a921c
RDX: 1ffff110040cab10 RSI: 0000000000000008 RDI: ffff888020523b00
RBP: ffff000000000000 R08: 0000000000000001 R09: ffff888020523b07
R10: ffffed10040a4760 R11: 0000000000000000 R12: ffff000000000000
R13: ffff000000000000 R14: ffff000000000000 R15: ffff000000000000
FS: 0000000000000000(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 000000000bc8e000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
0: 67 05 00 00 eb 13 addr32 add $0x13eb0000,%eax
6: 0f 1f 00 nopl (%rax)
9: 66 8c d0 mov %ss,%ax
c: 66 83 f8 18 cmp $0x18,%ax
10: 74 07 je 0x19
12: b8 18 00 00 00 mov $0x18,%eax
17: 8e d0 mov %eax,%ss
19: 48 83 c4 10 add $0x10,%rsp
1d: 4c 89 e0 mov %r12,%rax
20: 5b pop %rbx
21: 5d pop %rbp
22: 41 5c pop %r12
24: 41 5d pop %r13
26: 41 5e pop %r14
28: 41 5f pop %r15
* 2a: c3 retq <-- trapping instruction
2b: 48 8d bd 28 18 00 00 lea 0x1828(%rbp),%rdi
32: 48 b8 00 00 00 00 00 movabs $0xdffffc0000000000,%rax
39: fc ff df
3c: 48 89 fa mov %rdi,%rdx
3f: 48 rex.W
---
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-10 9:14 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=000000000000fe1d6705e5df7580@google.com \
--to=syzbot+95ea0d29692df9761488@syzkaller.appspotmail.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=mingo@redhat.com \
--cc=nathan@kernel.org \
--cc=peterz@infradead.org \
--cc=sfr@canb.auug.org.au \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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.