[v6.1] kernel panic: stack is corrupted in lockdep_hardirqs_on_prepare

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 0cbb5f65e52f Linux 6.1.128
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1358f718580000
kernel config: https://syzkaller.appspot.com/x/.config?x=ddc0722618a3964e
dashboard link: https://syzkaller.appspot.com/bug?extid=6d75aba1e2659a26241e
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/c6d849a518b0/disk-0cbb5f65.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/76ad82aaf432/vmlinux-0cbb5f65.xz
kernel image: https://storage.googleapis.com/syzbot-assets/5d4b74f07bf4/bzImage-0cbb5f65.xz

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

loop0: detected capacity change from 0 to 4096
ntfs3: loop0: Different NTFS' sector size (4096) and media sector size (512)
Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: lockdep_hardirqs_on_prepare+0x748/0x7a0
CPU: 1 PID: 5885 Comm: syz.0.481 Not tainted 6.1.128-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 12/27/2024
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
panic+0x318/0x764 kernel/panic.c:339
__stack_chk_fail+0x10/0x10 kernel/panic.c:767
lockdep_hardirqs_on_prepare+0x748/0x7a0
trace_hardirqs_on+0x34/0x40 kernel/trace/trace_preemptirq.c:49
native_save_fl arch/x86/include/asm/irqflags.h:22 [inline]
arch_local_save_flags arch/x86/include/asm/irqflags.h:70 [inline]
arch_irqs_disabled arch/x86/include/asm/irqflags.h:130 [inline]
seqcount_lockdep_reader_access+0x153/0x220 include/linux/seqlock.h:104
ktime_get_coarse_real_ts64+0x36/0x120 kernel/time/timekeeping.c:2261
current_time+0x87/0x300 fs/inode.c:2538
touch_atime+0x28b/0x680 fs/inode.c:2030
file_accessed include/linux/fs.h:2600 [inline]
filemap_read+0x2ef3/0x31d0 mm/filemap.c:2835
__kernel_read+0x421/0x890 fs/read_write.c:428
integrity_kernel_read+0xac/0xf0 security/integrity/iint.c:228
ima_calc_file_hash_tfm security/integrity/ima/ima_crypto.c:485 [inline]
ima_calc_file_shash security/integrity/ima/ima_crypto.c:516 [inline]
ima_calc_file_hash+0x163f/0x1d10 security/integrity/ima/ima_crypto.c:573
ima_collect_measurement+0x559/0xc40 security/integrity/ima/ima_api.c:293
process_measurement+0x135c/0x21b0 security/integrity/ima/ima_main.c:351
ima_file_check+0xed/0x170 security/integrity/ima/ima_main.c:534
do_open fs/namei.c:3628 [inline]
path_openat+0x2687/0x2e60 fs/namei.c:3783
do_filp_open+0x230/0x480 fs/namei.c:3810
do_sys_openat2+0x13b/0x4f0 fs/open.c:1318
do_sys_open fs/open.c:1334 [inline]
__do_sys_openat fs/open.c:1350 [inline]
__se_sys_openat fs/open.c:1345 [inline]
__x64_sys_openat+0x243/0x290 fs/open.c:1345
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f937e98cde9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 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:00007f937f7d2038 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00007f937eba5fa0 RCX: 00007f937e98cde9
RDX: 0000000000101042 RSI: 0000400000000040 RDI: ffffffffffffff9c
RBP: 00007f937ea0e2a0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000015 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007f937eba5fa0 R15: 00007ffc543c9c68
</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]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.