syzbot


kernel panic: stack is corrupted in lock_release

Status: closed as dup on 2019/01/04 11:20
Reported-by: syzbot+bc3cd5b4c1f71fc3c65d@syzkaller.appspotmail.com
First crash: 1500d, last: 1496d
Duplicate of (1):
Title Repro Cause bisect Fix bisect Count Last Reported
kernel panic: stack is corrupted in udp4_lib_lookup2 11 1501d 1497d
similar bugs (2):
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream kernel panic: stack is corrupted in lock_release (3) C error 8 9d08h 137d 0/24 upstream: reported C repro on 2022/09/25 10:47
upstream kernel panic: stack is corrupted in lock_release (2) syz error error 27 1208d 1256d 0/24 auto-obsoleted due to no activity on 2022/09/01 14:45

Sample crash report:
Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: lock_release+0x98e/0xc40 kernel/locking/lockdep.c:3864
CPU: 1 PID: 5196 Comm: syz-executor2 Not tainted 4.20.0+ #9
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
Kernel Offset: disabled
Rebooting in 86400 seconds..

Crashes (4):
Manager Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets Title
ci-upstream-kasan-gce-smack-root 2019/01/04 13:40 upstream 96d4f267e40f 7da23925 .config console log report
ci-upstream-kasan-gce-selinux-root 2019/01/02 12:25 upstream 8e143b90e4d4 f0491811 .config console log report
ci-upstream-kasan-gce-smack-root 2019/01/02 01:07 upstream 28e8c4bc8eb4 3d85f48c .config console log report
ci-upstream-kasan-gce-root 2018/12/31 13:07 upstream 195303136f19 2b42fdc8 .config console log report
* Struck through repros no longer work on HEAD.