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

3 views
Skip to first unread message

syzbot

unread,
Sep 9, 2024, 5:40:26 PM9/9/24
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 14e468424d3e Linux 5.15.166
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13badf29980000
kernel config: https://syzkaller.appspot.com/x/.config?x=8d58a8e8a6c2ab88
dashboard link: https://syzkaller.appspot.com/bug?extid=ea1188d46e8cb2e06abc
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/c745bbe4ebd8/disk-14e46842.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f07c263e8276/vmlinux-14e46842.xz
kernel image: https://storage.googleapis.com/syzbot-assets/511d53dfa858/bzImage-14e46842.xz

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

ntfs3: loop2: Different NTFS' sector size (1024) and media sector size (512)
Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: lock_is_held_type+0x17f/0x180
CPU: 1 PID: 4056 Comm: syz.2.75 Not tainted 5.15.166-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e3/0x2d0 lib/dump_stack.c:106
panic+0x318/0x860 kernel/panic.c:309
__stack_chk_fail+0x10/0x10 kernel/panic.c:761
lock_is_held_type+0x17f/0x180
lock_is_held include/linux/lockdep.h:287 [inline]
___might_sleep+0xf1/0x6a0 kernel/sched/core.c:9602
kmap include/linux/highmem-internal.h:155 [inline]
ntfs_map_page+0x5a/0x390 fs/ntfs/aops.h:78
ntfs_fill_super+0x361a/0x4340 fs/ntfs3/super.c:1147
get_tree_bdev+0x3fe/0x620 fs/super.c:1323
vfs_get_tree+0x88/0x270 fs/super.c:1528
do_new_mount+0x2ba/0xb40 fs/namespace.c:3005
do_mount fs/namespace.c:3348 [inline]
__do_sys_mount fs/namespace.c:3556 [inline]
__se_sys_mount+0x2d5/0x3c0 fs/namespace.c:3533
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f8a8ac3269a
Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb a6 e8 de 1a 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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f8a890a9e68 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007f8a890a9ef0 RCX: 00007f8a8ac3269a
RDX: 000000002001f800 RSI: 0000000020000000 RDI: 00007f8a890a9eb0
RBP: 000000002001f800 R08: 00007f8a890a9ef0 R09: 0000000000800840
R10: 0000000000800840 R11: 0000000000000246 R12: 0000000020000000
R13: 00007f8a890a9eb0 R14: 000000000001f85d R15: 0000000020000080
</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 report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

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

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

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

syzbot

unread,
Apr 28, 2025, 11:07:31 AM4/28/25
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:

HEAD commit: f7347f400572 Linux 5.15.180
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13485374580000
kernel config: https://syzkaller.appspot.com/x/.config?x=e0a09dd23d715b59
dashboard link: https://syzkaller.appspot.com/bug?extid=ea1188d46e8cb2e06abc
compiler: Debian clang version 20.1.2 (++20250402124445+58df0ef89dd6-1~exp1~20250402004600.97), Debian LLD 20.1.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=154f6374580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/f174a25d1f90/disk-f7347f40.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/2b5ffc4e5dc3/vmlinux-f7347f40.xz
kernel image: https://storage.googleapis.com/syzbot-assets/b48f40123eb9/bzImage-f7347f40.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/e26e56c2bc78/mount_0.gz

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

loop1: detected capacity change from 0 to 4096
Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: lock_is_held_type+0x182/0x190 kernel/locking/lockdep.c:-1
CPU: 1 PID: 4884 Comm: syz.1.255 Not tainted 5.15.180-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
Call Trace:
<TASK>
dump_stack_lvl+0x168/0x230 lib/dump_stack.c:106
panic+0x2c9/0x7f0 kernel/panic.c:309
__stack_chk_fail+0x10/0x10 kernel/panic.c:761
lock_is_held_type+0x182/0x190 kernel/locking/lockdep.c:-1
lock_is_held include/linux/lockdep.h:287 [inline]
___might_sleep+0xa3/0x600 kernel/sched/core.c:9605
kmap include/linux/highmem-internal.h:155 [inline]
ntfs_map_page+0x59/0x390 fs/ntfs/aops.h:78
ntfs_fill_super+0x2fed/0x3c10 fs/ntfs3/super.c:1147
get_tree_bdev+0x3f1/0x610 fs/super.c:1325
vfs_get_tree+0x88/0x270 fs/super.c:1530
do_new_mount+0x24a/0xa40 fs/namespace.c:3012
do_mount fs/namespace.c:3355 [inline]
__do_sys_mount fs/namespace.c:3563 [inline]
__se_sys_mount+0x2d6/0x3c0 fs/namespace.c:3540
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f48508e810a
Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb a6 e8 de 1a 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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f484fb55e68 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007f484fb55ef0 RCX: 00007f48508e810a
RDX: 0000200000000000 RSI: 0000200000000280 RDI: 00007f484fb55eb0
RBP: 0000200000000000 R08: 00007f484fb55ef0 R09: 0000000002010c14
R10: 0000000002010c14 R11: 0000000000000246 R12: 0000200000000280
R13: 00007f484fb55eb0 R14: 000000000001f75b R15: 00002000000000c0
</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,
Nov 18, 2025, 12:58:16 AM11/18/25
to syzkaller...@googlegroups.com
Auto-closing this bug as obsolete.
No recent activity, existing reproducers are no longer triggering the issue.
Reply all
Reply to author
Forward
0 new messages