[v5.15] kernel panic: stack is corrupted in lock_acquire

0 views
Skip to first unread message

syzbot

unread,
May 20, 2023, 8:30:49 AM5/20/23
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 9d6bde853685 Linux 5.15.112
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1490ae5a280000
kernel config: https://syzkaller.appspot.com/x/.config?x=a61e8195d8bdf36e
dashboard link: https://syzkaller.appspot.com/bug?extid=36d9632fc4eac47cba41
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/b65d6c2ec328/disk-9d6bde85.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/cf811ebac37b/vmlinux-9d6bde85.xz
kernel image: https://storage.googleapis.com/syzbot-assets/b2f32fdecf97/bzImage-9d6bde85.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+36d963...@syzkaller.appspotmail.com

Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: lock_acquire+0x4e9/0x4f0
CPU: 1 PID: 28362 Comm: syz-executor.4 Not tainted 5.15.112-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/28/2023
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
panic+0x318/0x84d kernel/panic.c:309
__stack_chk_fail+0x10/0x10 kernel/panic.c:753
lock_acquire+0x4e9/0x4f0
__raw_spin_lock_irq include/linux/spinlock_api_smp.h:128 [inline]
_raw_spin_lock_irq+0xcf/0x110 kernel/locking/spinlock.c:170
spin_lock_irq include/linux/spinlock.h:388 [inline]
truncate_inode_pages_final+0x5f/0x90 mm/truncate.c:456
ntfs_evict_inode+0x18/0xb0 fs/ntfs3/inode.c:1772
evict+0x2a4/0x620 fs/inode.c:587
ntfs_fill_super+0x3c3f/0x4450 fs/ntfs3/super.c:1185
get_tree_bdev+0x3fe/0x620 fs/super.c:1303
vfs_get_tree+0x88/0x270 fs/super.c:1508
do_new_mount+0x28b/0xad0 fs/namespace.c:2994
do_mount fs/namespace.c:3337 [inline]
__do_sys_mount fs/namespace.c:3545 [inline]
__se_sys_mount+0x2d5/0x3c0 fs/namespace.c:3522
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7f656f0d769a
Code: 48 c7 c2 b8 ff ff ff f7 d8 64 89 02 b8 ff ff ff ff eb d2 e8 b8 04 00 00 0f 1f 84 00 00 00 00 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f656d647f88 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 000000000001f329 RCX: 00007f656f0d769a
RDX: 000000002001f340 RSI: 000000002001f380 RDI: 00007f656d647fe0
RBP: 00007f656d648020 R08: 00007f656d648020 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000202 R12: 000000002001f340
R13: 000000002001f380 R14: 00007f656d647fe0 R15: 000000002001f3c0
</TASK>
Kernel Offset: disabled
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 syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to change bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

syzbot

unread,
Jul 6, 2023, 8:23:53 PM7/6/23
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:

HEAD commit: d54cfc420586 Linux 5.15.120
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13b7e8f2a80000
kernel config: https://syzkaller.appspot.com/x/.config?x=c67dae6b27f0d6cd
dashboard link: https://syzkaller.appspot.com/bug?extid=36d9632fc4eac47cba41
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11407d78a80000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/4aa2cbf1e81c/disk-d54cfc42.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/2ebee78b098c/vmlinux-d54cfc42.xz
kernel image: https://storage.googleapis.com/syzbot-assets/4e17f9ac4b6a/bzImage-d54cfc42.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/0dd9c0a0c489/mount_0.gz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+36d963...@syzkaller.appspotmail.com

ntfs3: loop0: Different NTFS' sector size (1024) and media sector size (512)
Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: lock_acquire+0x4e9/0x4f0
CPU: 0 PID: 3659 Comm: syz-executor.0 Not tainted 5.15.120-syzkaller #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+0x1e3/0x2cb lib/dump_stack.c:106
panic+0x318/0x84d kernel/panic.c:309
__stack_chk_fail+0x10/0x10 kernel/panic.c:753
lock_acquire+0x4e9/0x4f0
__raw_spin_lock_irq include/linux/spinlock_api_smp.h:128 [inline]
_raw_spin_lock_irq+0xcf/0x110 kernel/locking/spinlock.c:170
spin_lock_irq include/linux/spinlock.h:388 [inline]
truncate_inode_pages_final+0x5f/0x90 mm/truncate.c:456
ntfs_evict_inode+0x18/0xb0 fs/ntfs3/inode.c:1778
evict+0x2a4/0x620 fs/inode.c:587
ntfs_fill_super+0x3c3f/0x4450 fs/ntfs3/super.c:1185
get_tree_bdev+0x3fe/0x620 fs/super.c:1303
vfs_get_tree+0x88/0x270 fs/super.c:1508
do_new_mount+0x28b/0xae0 fs/namespace.c:2994
do_mount fs/namespace.c:3337 [inline]
__do_sys_mount fs/namespace.c:3545 [inline]
__se_sys_mount+0x2d5/0x3c0 fs/namespace.c:3522
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7fc2bec558ba
Code: 48 c7 c2 b8 ff ff ff f7 d8 64 89 02 b8 ff ff ff ff eb d2 e8 b8 04 00 00 0f 1f 84 00 00 00 00 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fc2bdfc5f88 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 000000000001f6e6 RCX: 00007fc2bec558ba
RDX: 000000002001f700 RSI: 000000002001f740 RDI: 00007fc2bdfc5fe0
RBP: 00007fc2bdfc6020 R08: 00007fc2bdfc6020 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 000000002001f700
R13: 000000002001f740 R14: 00007fc2bdfc5fe0 R15: 000000002001f780
</TASK>
Kernel Offset: disabled
Rebooting in 86400 seconds..


---
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

syzbot

unread,
Aug 6, 2023, 9:59:42 PM8/6/23
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:

HEAD commit: 38d4ca22a528 Linux 5.15.124
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1068b171a80000
kernel config: https://syzkaller.appspot.com/x/.config?x=45eb463798d34fdb
dashboard link: https://syzkaller.appspot.com/bug?extid=36d9632fc4eac47cba41
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=178e3533a80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16d7f55da80000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/0470c022da0e/disk-38d4ca22.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/56cf48a83529/vmlinux-38d4ca22.xz
kernel image: https://storage.googleapis.com/syzbot-assets/ac8ac64c33ec/bzImage-38d4ca22.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/5e57b3ac6586/mount_0.gz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+36d963...@syzkaller.appspotmail.com

Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: lock_acquire+0x4e9/0x4f0
CPU: 1 PID: 4267 Comm: syz-executor313 Not tainted 5.15.124-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2023
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
panic+0x318/0x84d kernel/panic.c:309
__stack_chk_fail+0x10/0x10 kernel/panic.c:753
lock_acquire+0x4e9/0x4f0
__raw_spin_lock_irq include/linux/spinlock_api_smp.h:128 [inline]
_raw_spin_lock_irq+0xcf/0x110 kernel/locking/spinlock.c:170
spin_lock_irq include/linux/spinlock.h:388 [inline]
truncate_inode_pages_final+0x5f/0x90 mm/truncate.c:456
ntfs_evict_inode+0x18/0xb0 fs/ntfs3/inode.c:1780
evict+0x2a4/0x620 fs/inode.c:587
ntfs_fill_super+0x3c3f/0x4450 fs/ntfs3/super.c:1185
get_tree_bdev+0x3fe/0x620 fs/super.c:1303
vfs_get_tree+0x88/0x270 fs/super.c:1508
do_new_mount+0x28b/0xae0 fs/namespace.c:2994
do_mount fs/namespace.c:3337 [inline]
__do_sys_mount fs/namespace.c:3545 [inline]
__se_sys_mount+0x2d5/0x3c0 fs/namespace.c:3522
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7f304ce0ea3a
Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb a6 e8 1e 09 00 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffef750d678 EFLAGS: 00000286 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f304ce0ea3a
RDX: 00000000200000c0 RSI: 000000002001f840 RDI: 00007ffef750d6d0
RBP: 0000000000000004 R08: 00007ffef750d710 R09: 000000000001f802
R10: 0000000000008058 R11: 0000000000000286 R12: 00007ffef750d710
R13: 0000000000200000 R14: 0000000000000003 R15: 0000000000008058
</TASK>
Kernel Offset: disabled
Rebooting in 86400 seconds..


---
Reply all
Reply to author
Forward
0 new messages