From: syzbot <syzbot+c2fb6f9ddcea95ba49b5@syzkaller.appspotmail.com>
To: bp@alien8.de, hpa@zytor.com, jannh@google.com,
jpoimboe@redhat.com, linux-kernel@vger.kernel.org,
mingo@redhat.com, netdev@vger.kernel.org, peterz@infradead.org,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
x86@kernel.org
Subject: BUG: stack guard page was hit in update_stack_state
Date: Mon, 03 Feb 2020 20:43:11 -0800 [thread overview]
Message-ID: <0000000000005cad20059db8adba@google.com> (raw)
Hello,
syzbot found the following crash on:
HEAD commit: b3a60822 Merge branch 'for-v5.6' of git://git.kernel.org:/..
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=147ae5f1e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=614e56d86457f3a7
dashboard link: https://syzkaller.appspot.com/bug?extid=c2fb6f9ddcea95ba49b5
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
Unfortunately, I don't have any reproducer for this crash yet.
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+c2fb6f9ddcea95ba49b5@syzkaller.appspotmail.com
8021q: adding VLAN 0 to HW filter on device bond40
BUG: stack guard page was hit at 0000000018e8ec40 (stack is 000000008cfdf90e..000000000f88bd28)
kernel stack overflow (double-fault): 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 28658 Comm: syz-executor.3 Not tainted 5.5.0-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:update_stack_state+0x4b/0x5f0 arch/x86/kernel/unwind_frame.c:194
Code: fd 41 54 49 8d 0c 06 53 48 81 ec a0 00 00 00 48 c7 45 80 42 54 41 89 48 c7 85 78 ff ff ff b3 8a b5 41 48 c7 45 88 00 3f 33 81 <48> 89 b5 68 ff ff ff c7 01 f1 f1 f1 f1 c7 41 04 00 f3 f3 f3 48 89
RSP: 0018:ffffc9000769ffc0 EFLAGS: 00010286
RAX: dffffc0000000000 RBX: ffffc900076a01a8 RCX: fffff52000ed4000
RDX: 1ffff92000ed4033 RSI: ffffc900076a0230 RDI: ffffc900076a01a8
RBP: ffffc900076a0088 R08: ffffc900076a01d0 R09: ffffc900076a0200
R10: ffffc900076a01d0 R11: ffffc900076a01e0 R12: 1ffff92000ed4018
R13: ffffc900076a01a8 R14: 1ffff92000ed4000 R15: ffffc900076a0230
FS: 00007fd172d8f700(0000) GS:ffff8880ae800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffc9000769ffb8 CR3: 0000000097238000 CR4: 00000000001406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
Modules linked in:
---[ end trace 04286e13cba26a71 ]---
RIP: 0010:update_stack_state+0x4b/0x5f0 arch/x86/kernel/unwind_frame.c:194
Code: fd 41 54 49 8d 0c 06 53 48 81 ec a0 00 00 00 48 c7 45 80 42 54 41 89 48 c7 85 78 ff ff ff b3 8a b5 41 48 c7 45 88 00 3f 33 81 <48> 89 b5 68 ff ff ff c7 01 f1 f1 f1 f1 c7 41 04 00 f3 f3 f3 48 89
RSP: 0018:ffffc9000769ffc0 EFLAGS: 00010286
RAX: dffffc0000000000 RBX: ffffc900076a01a8 RCX: fffff52000ed4000
RDX: 1ffff92000ed4033 RSI: ffffc900076a0230 RDI: ffffc900076a01a8
RBP: ffffc900076a0088 R08: ffffc900076a01d0 R09: ffffc900076a0200
R10: ffffc900076a01d0 R11: ffffc900076a01e0 R12: 1ffff92000ed4018
R13: ffffc900076a01a8 R14: 1ffff92000ed4000 R15: ffffc900076a0230
FS: 00007fd172d8f700(0000) GS:ffff8880ae800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffc9000769ffb8 CR3: 0000000097238000 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.
next reply other threads:[~2020-02-04 4:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-04 4:43 syzbot [this message]
2020-02-04 13:02 ` unbounded recursion through bond_netdev_event notifier? [was: BUG: stack guard page was hit in update_stack_state] Jann Horn
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=0000000000005cad20059db8adba@google.com \
--to=syzbot+c2fb6f9ddcea95ba49b5@syzkaller.appspotmail.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=jannh@google.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).