kernel panic: stack is corrupted in lock_release (2)

0 views
Skip to first unread message

syzbot

unread,
Jul 22, 2019, 9:08:06 PM7/22/19
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following crash on:

HEAD commit: 49d05fe2 ipv6: rt6_check should return NULL if 'from' is N..
git tree: net
console output: https://syzkaller.appspot.com/x/log.txt?x=11b35fe0600000
kernel config: https://syzkaller.appspot.com/x/.config?x=87305c3ca9c25c70
dashboard link: https://syzkaller.appspot.com/bug?extid=c29eee02105e7149b0d7
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
CC: [net...@vger.kernel.org]

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+c29eee...@syzkaller.appspotmail.com

Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in:
lock_release+0x866/0x960 /kernel/locking/lockdep.c:4436
CPU: 0 PID: 30026 Comm: blkid Not tainted 5.2.0+ #91
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
Call Trace:
Shutting down cpus with NMI
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 syzk...@googlegroups.com.

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

syzbot

unread,
Sep 1, 2019, 7:27:04 PM9/1/19
to syzkaller-upst...@googlegroups.com
Sending this report upstream.
Reply all
Reply to author
Forward
0 new messages