From: syzbot <syzbot+83979935eb6304f8cd46@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: kernel panic: stack is corrupted in __lock_acquire (4)
Date: Mon, 10 Jun 2019 01:54:06 -0700 [thread overview]
Message-ID: <0000000000009b3b80058af452ae@google.com> (raw)
Hello,
syzbot found the following crash on:
HEAD commit: fdf71426 net: fix indirect calls helpers for ptype list ho..
git tree: net
console output: https://syzkaller.appspot.com/x/log.txt?x=1199f551a00000
kernel config: https://syzkaller.appspot.com/x/.config?x=4f721a391cd46ea
dashboard link: https://syzkaller.appspot.com/bug?extid=83979935eb6304f8cd46
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+83979935eb6304f8cd46@syzkaller.appspotmail.com
Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in:
__lock_acquire+0x3959/0x5490 kernel/locking/lockdep.c:3820
CPU: 1 PID: 11196 Comm: syz-executor.0 Not tainted 5.2.0-rc2+ #41
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
Call Trace:
Kernel Offset: disabled
Rebooting in 86400 seconds..
---
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:[~2019-06-10 8:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-10 8:54 syzbot [this message]
2019-09-01 22:48 ` kernel panic: stack is corrupted in __lock_acquire (4) syzbot
2019-09-02 3:23 ` Dmitry Vyukov
2019-10-17 16:25 ` Eric Biggers
2019-10-17 16:30 ` Eric Biggers
2019-11-19 5:29 ` Eric Biggers
2019-11-19 5:46 ` John Fastabend
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=0000000000009b3b80058af452ae@google.com \
--to=syzbot+83979935eb6304f8cd46@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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 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).