syzbot


kernel panic: stack is corrupted in pointer

Status: closed as dup on 2019/07/23 07:39
Subsystems: kernel
[Documentation on labels]
Reported-by: syzbot+79f5f028005a77ecb6bb@syzkaller.appspotmail.com
First crash: 1769d, last: 1769d
Cause bisection: introduced by (bisect log) :
commit 96a5d8d4915f3e241ebb48d5decdd110ab9c7dcf
Author: Leo Liu <leo.liu@amd.com>
Date: Fri Jul 13 15:26:28 2018 +0000

  drm/amdgpu: Make sure IB tests flushed after IP resume

Crash: KASAN: use-after-free Read in psock_map_pop (log)
Repro: syz .config
  
Duplicate of
Title Repro Cause bisect Fix bisect Count Last Reported
kernel panic: corrupted stack end in dput fs syz done 1 1784d 1784d
Discussions (1)
Title Replies (including bot) Last reply
kernel panic: stack is corrupted in pointer 5 (8) 2019/07/24 16:22
Last patch testing requests (1)
Created Duration User Patch Repo Result
2019/07/23 17:34 17m john.fastabend@gmail.com bpf OK

Sample crash report:
Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: pointer+0x702/0x750 lib/vsprintf.c:2187
Shutting down cpus with NMI
Kernel Offset: disabled

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2019/07/16 14:59 linux-next 1438cde7c87c db842eb6 .config console log report syz ci-upstream-linux-next-kasan-gce-root
* Struck through repros no longer work on HEAD.