BUG: stack guard page was hit in error_entry

11 views
Skip to first unread message

syzbot

unread,
Sep 9, 2020, 4:09:23 AM9/9/20
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: c70672d8 Merge tag 's390-5.9-5' of git://git.kernel.org/pu..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=11cd3819900000
kernel config: https://syzkaller.appspot.com/x/.config?x=bd46548257448703
dashboard link: https://syzkaller.appspot.com/bug?extid=6c7ab6773c265042872e
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+6c7ab6...@syzkaller.appspotmail.com

BUG: stack guard page was hit at 000000004c6030c4 (stack is 00000000e9bcb94e..000000001952673e)
kernel stack overflow (double-fault): 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 21764 Comm: kworker/u4:3 Not tainted 5.9.0-rc3-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: bat_events batadv_nc_worker
RIP: 0010:error_entry+0x1b/0xc0 arch/x86/entry/entry_64.S:931
Code: fd ff ff 0f 01 f8 e9 e4 fd ff ff 0f 1f 40 00 fc 56 48 8b 74 24 08 48 89 7c 24 08 52 51 50 41 50 41 51 41 52 41 53 53 55 41 54 <41> 55 41 56 41 57 56 31 d2 31 c9 45 31 c0 45 31 c9 45 31 d2 45 31
RSP: 0018:ffffc90016990000 EFLAGS: 00010046
RAX: 0000000000000001 RBX: 0000000000000000 RCX: 1ffffffff1308b20
RDX: dffffc0000000000 RSI: ffffffff88000a68 RDI: 0000000000000082
RBP: ffffc90016990098 R08: 0000000000000000 R09: ffffffff8ab2680f
R10: fffffbfff1564d01 R11: 0000000000000000 R12: 0000000000000002
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
FS: 0000000000000000(0000) GS:ffff8880ae600000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffc9001698fff8 CR3: 000000009819f000 CR4: 00000000001526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
Lost 392 message(s)!
---[ end trace 1074aab1c17bb06b ]---
RIP: 0010:error_entry+0x1b/0xc0 arch/x86/entry/entry_64.S:931
Code: fd ff ff 0f 01 f8 e9 e4 fd ff ff 0f 1f 40 00 fc 56 48 8b 74 24 08 48 89 7c 24 08 52 51 50 41 50 41 51 41 52 41 53 53 55 41 54 <41> 55 41 56 41 57 56 31 d2 31 c9 45 31 c0 45 31 c9 45 31 d2 45 31
RSP: 0018:ffffc90016990000 EFLAGS: 00010046
RAX: 0000000000000001 RBX: 0000000000000000 RCX: 1ffffffff1308b20
RDX: dffffc0000000000 RSI: ffffffff88000a68 RDI: 0000000000000082
RBP: ffffc90016990098 R08: 0000000000000000 R09: ffffffff8ab2680f
R10: fffffbfff1564d01 R11: 0000000000000000 R12: 0000000000000002
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
FS: 0000000000000000(0000) GS:ffff8880ae600000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffc9001698fff8 CR3: 000000009819f000 CR4: 00000000001526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


---
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 syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

syzbot

unread,
Dec 4, 2020, 3:02:19 AM12/4/20
to syzkaller-upst...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages