Title | Replies (including bot) | Last reply |
---|---|---|
[syzbot] [mm?] [reiserfs?] kernel panic: stack is corrupted in ___slab_alloc | 6 (8) | 2024/03/03 09:21 |
syzbot |
sign-in | mailing list | source | docs |
Title | Replies (including bot) | Last reply |
---|---|---|
[syzbot] [mm?] [reiserfs?] kernel panic: stack is corrupted in ___slab_alloc | 6 (8) | 2024/03/03 09:21 |
Created | Duration | User | Patch | Repo | Result |
---|---|---|---|---|---|
2024/03/03 01:32 | 7h47m | bisect fix | upstream | OK (1) job log | |
2024/01/06 21:46 | 4h19m | bisect fix | upstream | OK (0) job log log | |
2023/12/07 17:27 | 3h07m | bisect fix | upstream | OK (0) job log log | |
2023/11/06 18:26 | 3h06m | bisect fix | upstream | OK (0) job log log | |
2023/10/07 05:29 | 6h17m | bisect fix | upstream | OK (0) job log log | |
2023/08/08 22:34 | 2h31m | bisect fix | upstream | OK (0) job log log |
Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: ___slab_alloc+0x12c3/0x1400 mm/slub.c:3270 CPU: 0 PID: 5009 Comm: syz-executor248 Not tainted 6.4.0-syzkaller-01406-ge8f75c0270d9 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/27/2023 Call Trace: <TASK> __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0xd9/0x150 lib/dump_stack.c:106 panic+0x686/0x730 kernel/panic.c:340 __stack_chk_fail+0x19/0x20 kernel/panic.c:759 ___slab_alloc+0x12c3/0x1400 mm/slub.c:3270
Time | Kernel | Commit | Syzkaller | Config | Log | Report | Syz repro | C repro | VM info | Assets (help?) | Manager | Title |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2023/06/28 17:10 | upstream | e8f75c0270d9 | 8064cb02 | .config | console log | report | syz | C | [disk image] [vmlinux] [kernel image] [mounted in repro] | ci-upstream-kasan-gce-root | kernel panic: stack is corrupted in ___slab_alloc |