syzbot


kernel panic: stack is corrupted in __lock_acquire (2)

Status: closed as invalid on 2019/05/25 17:37
Subsystems: kernel
[Documentation on labels]
First crash: 1793d, last: 1793d
Similar bugs (4)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream kernel panic: stack is corrupted in __lock_acquire (5) ntfs3 C error done 18 105d 482d 26/26 fixed on 2024/02/21 18:23
upstream kernel panic: stack is corrupted in __lock_acquire (3) kernel 3 1782d 1782d 0/26 closed as invalid on 2019/06/05 18:41
upstream kernel panic: stack is corrupted in __lock_acquire (4) kernel syz error error 75 1620d 1777d 15/26 fixed on 2020/02/18 14:31
upstream kernel panic: stack is corrupted in __lock_acquire kernel 9 1924d 1936d 0/26 closed as dup on 2019/01/04 11:22

Sample crash report:
Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: __lock_acquire+0x3959/0x5490 kernel/locking/lockdep.c:3820
CPU: 0 PID: 11717 Comm: syz-executor.1 Not tainted 5.2.0-rc1+ #6
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
Kernel Offset: disabled
Rebooting in 86400 seconds..

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2019/05/25 07:52 net-next-old af5136f95045 85c57315 .config console log report ci-upstream-net-kasan-gce
* Struck through repros no longer work on HEAD.