lkml.org 
[lkml]   [2022]   [Nov]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Date
SubjectRe: [syzbot] kernel panic: stack is corrupted in __blk_flush_plug
On Tue, 15 Nov 2022 at 23:48, syzbot
<syzbot+fade8a8e2bdc29b3a90b@syzkaller.appspotmail.com> wrote:
>
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 9e4ce762f0e7 Merge branches 'for-next/acpi', 'for-next/asm..
> git tree: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
> console output: https://syzkaller.appspot.com/x/log.txt?x=1502ad35880000
> kernel config: https://syzkaller.appspot.com/x/.config?x=20ffacc1ce1c99b5
> dashboard link: https://syzkaller.appspot.com/bug?extid=fade8a8e2bdc29b3a90b
> compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
> userspace arch: arm64
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14f33159880000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13e33ef1880000
>
> Downloadable assets:
> disk image: https://storage.googleapis.com/syzbot-assets/a70eb29add74/disk-9e4ce762.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/769d096516a8/vmlinux-9e4ce762.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/9309615f51d5/Image-9e4ce762.gz.xz
> mounted in repro: https://storage.googleapis.com/syzbot-assets/0332fee8ec34/mount_0.gz

The reproducer mounts ntfs3, so I think it's related to ntfs3. +maintainers.


> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+fade8a8e2bdc29b3a90b@syzkaller.appspotmail.com
>
> 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: 4370 Comm: syz-executor220 Not tainted 6.1.0-rc5-syzkaller-32254-g9e4ce762f0e7 #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..
>
>
> ---
> This report is generated by a bot. It may contain errors.
> See https://goo.gl/tpsmEJ for more information about syzbot.
> syzbot engineers can be reached at syzkaller@googlegroups.com.
>
> syzbot will keep track of this issue. See:
> https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
> syzbot can test patches for this issue, for details see:
> https://goo.gl/tpsmEJ#testing-patches

\
 
 \ /
  Last update: 2022-11-16 12:13    [W:0.045 / U:0.420 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site