From: syzbot <syzbot+83979935eb6304f8cd46@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: kernel panic: stack is corrupted in __lock_acquire (4)
Date: Sun, 01 Sep 2019 15:48:06 -0700 [thread overview]
Message-ID: <0000000000000ec274059185a63e@google.com> (raw)
In-Reply-To: <0000000000009b3b80058af452ae@google.com>
syzbot has found a reproducer for the following crash on:
HEAD commit: 38320f69 Merge branch 'Minor-cleanup-in-devlink'
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=13d74356600000
kernel config: https://syzkaller.appspot.com/x/.config?x=1bbf70b6300045af
dashboard link: https://syzkaller.appspot.com/bug?extid=83979935eb6304f8cd46
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1008b232600000
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+0x36fa/0x4c30 kernel/locking/lockdep.c:3907
CPU: 0 PID: 8662 Comm: syz-executor.4 Not tainted 5.3.0-rc6+ #153
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
Call Trace:
Kernel Offset: disabled
Rebooting in 86400 seconds..
next prev parent reply other threads:[~2019-09-01 22:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-10 8:54 kernel panic: stack is corrupted in __lock_acquire (4) syzbot
2019-09-01 22:48 ` syzbot [this message]
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=0000000000000ec274059185a63e@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).