From: syzbot <syzbot+fe6eeea133f070606074@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
linux@dominikbrodowski.net, mhiramat@kernel.org,
rostedt@goodmis.org, syzkaller-bugs@googlegroups.com
Subject: general protection fault in __switch_to_asm
Date: Wed, 10 Jun 2020 03:03:11 -0700 [thread overview]
Message-ID: <0000000000009dd95205a7b7f3bf@google.com> (raw)
Hello,
syzbot found the following crash on:
HEAD commit: e7b08814 Add linux-next specific files for 20200529
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=14a1f451100000
kernel config: https://syzkaller.appspot.com/x/.config?x=1e62421a5de6da96
dashboard link: https://syzkaller.appspot.com/bug?extid=fe6eeea133f070606074
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1524ea96100000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17fab432100000
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+fe6eeea133f070606074@syzkaller.appspotmail.com
general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] PREEMPT SMP KASAN
KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]
CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.7.0-rc7-next-20200529-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:__switch_to_asm+0x0/0x40 arch/x86/entry/entry_64.S:228
Code: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 <00> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
RSP: 0018:ffffffff89a07cd8 EFLAGS: 00010046
RAX: dffffc0000000000 RBX: ffff88809fce2b40 RCX: 1ffffffff1350dc9
RDX: 1ffff11015cc6fc2 RSI: ffff88809489e280 RDI: ffffffff89a86580
RBP: ffffffff89a07da8 R08: 0000000000000000 R09: fffffbfff155b432
R10: ffffffff8aada18f R11: fffffbfff155b431 R12: ffffffff89a86580
R13: ffff8880ae637e00 R14: ffff88809489e280 R15: ffff8880ae637e18
FS: 0000000000000000(0000) GS:ffff8880ae600000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000563f12be20f8 CR3: 000000009a876000 CR4: 00000000001406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
context_switch kernel/sched/core.c:3430 [inline]
__schedule+0x8f3/0x1f80 kernel/sched/core.c:4155
schedule_idle+0x53/0x90 kernel/sched/core.c:4258
do_idle+0x327/0x690 kernel/sched/idle.c:297
cpu_startup_entry+0x14/0x20 kernel/sched/idle.c:365
start_kernel+0x9be/0x9fb init/main.c:1043
secondary_startup_64+0xa4/0xb0 arch/x86/kernel/head_64.S:243
Modules linked in:
---[ end trace 7e4004b4996f54a3 ]---
RIP: 0010:__switch_to_asm+0x0/0x40 arch/x86/entry/entry_64.S:228
Code: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 <00> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
RSP: 0018:ffffffff89a07cd8 EFLAGS: 00010046
RAX: dffffc0000000000 RBX: ffff88809fce2b40 RCX: 1ffffffff1350dc9
RDX: 1ffff11015cc6fc2 RSI: ffff88809489e280 RDI: ffffffff89a86580
RBP: ffffffff89a07da8 R08: 0000000000000000 R09: fffffbfff155b432
R10: ffffffff8aada18f R11: fffffbfff155b431 R12: ffffffff89a86580
R13: ffff8880ae637e00 R14: ffff88809489e280 R15: ffff8880ae637e18
FS: 0000000000000000(0000) GS:ffff8880ae600000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000563f12be20f8 CR3: 000000009a876000 CR4: 00000000001406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
---
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.
syzbot can test patches for this bug, for details see:
https://goo.gl/tpsmEJ#testing-patches
next reply other threads:[~2020-06-10 10:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-10 10:03 syzbot [this message]
2020-10-20 6:48 ` general protection fault in __switch_to_asm syzbot
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=0000000000009dd95205a7b7f3bf@google.com \
--to=syzbot+fe6eeea133f070606074@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.org \
--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 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.