syzbot
kernel panic: stack is corrupted in __blk_flush_plug
Status:
auto-obsoleted due to no activity on 2023/03/21 02:15
Subsystems:
arm
ntfs3
[Documentation on labels]
Reported-by: syzbot+fade8a8e2bdc29b3a90b@syzkaller.appspotmail.com
First crash: 1357d, last: 1352d
▶
▼
Last patch testing requests (2)
Sample crash report:
loop0: detected capacity change from 0 to 8226
ntfs3: loop0: Mark volume as dirty due to NTFS errors
ntfs3: loop0: Failed to load $Extend.
Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: __blk_flush_plug+0x1a4/0x1a4
CPU: 0 PID: 5561 Comm: syz-executor281 Not tainted 6.1.0-rc5-syzkaller-32269-g9500fc6e9e60 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/30/2022
Call trace:
dump_backtrace+0x1c4/0x1f0 arch/arm64/kernel/stacktrace.c:156
show_stack+0x2c/0x54 arch/arm64/kernel/stacktrace.c:163
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x104/0x16c lib/dump_stack.c:106
dump_stack+0x1c/0x58 lib/dump_stack.c:113
panic+0x218/0x508 kernel/panic.c:274
warn_bogus_irq_restore+0x0/0x40 kernel/panic.c:703
blk_finish_plug+0x0/0x54
SMP: stopping secondary CPUs
Kernel Offset: disabled
CPU features: 0x00000,040e0108,4c017203
Memory Limit: none
Rebooting in 86400 seconds..
* Struck through repros no longer work on HEAD.