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

0 views
Skip to first unread message

syzbot

unread,
Apr 22, 2023, 1:52:55 PM4/22/23
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: f17b0ab65d17 Linux 6.1.25
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=109a108bc80000
kernel config: https://syzkaller.appspot.com/x/.config?x=d75954dcbfe38186
dashboard link: https://syzkaller.appspot.com/bug?extid=f21ed0bcae74330986e2
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/832d07d855e3/disk-f17b0ab6.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/4815c4c1f51b/vmlinux-f17b0ab6.xz
kernel image: https://storage.googleapis.com/syzbot-assets/4d6d025222b4/bzImage-f17b0ab6.xz

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

loop1: detected capacity change from 0 to 4096
ntfs3: loop1: Different NTFS' sector size (4096) and media sector size (512)
Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: lock_acquire+0x567/0x5a0
CPU: 0 PID: 14833 Comm: syz-executor.1 Not tainted 6.1.25-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/14/2023
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
panic+0x318/0x75d kernel/panic.c:339
__stack_chk_fail+0x10/0x10 kernel/panic.c:758
lock_acquire+0x567/0x5a0
seqcount_lockdep_reader_access+0x13b/0x220 include/linux/seqlock.h:103
ktime_get_coarse_real_ts64+0x36/0x120 kernel/time/timekeeping.c:2261
current_time+0x87/0x2f0 fs/inode.c:2451
touch_atime+0x28b/0x680 fs/inode.c:1943
file_accessed include/linux/fs.h:2535 [inline]
filemap_read+0x2ef3/0x31d0 mm/filemap.c:2744
__kernel_read+0x41e/0x8a0 fs/read_write.c:428
integrity_kernel_read+0xac/0xf0 security/integrity/iint.c:199
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+0xa57/0x1c00 security/integrity/ima/ima_crypto.c:573
ima_collect_measurement+0x4d4/0x970 security/integrity/ima/ima_api.c:292
process_measurement+0x1018/0x1cf0 security/integrity/ima/ima_main.c:337
ima_file_check+0xed/0x170 security/integrity/ima/ima_main.c:520
do_open fs/namei.c:3559 [inline]
path_openat+0x2687/0x2e60 fs/namei.c:3714
do_filp_open+0x230/0x480 fs/namei.c:3741
do_sys_openat2+0x13b/0x500 fs/open.c:1310
do_sys_open fs/open.c:1326 [inline]
__do_sys_open fs/open.c:1334 [inline]
__se_sys_open fs/open.c:1330 [inline]
__x64_sys_open+0x221/0x270 fs/open.c:1330
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+0x63/0xcd
RIP: 0033:0x7f234808c169
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 19 00 00 90 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 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f2348e06168 EFLAGS: 00000246 ORIG_RAX: 0000000000000002
RAX: ffffffffffffffda RBX: 00007f23481abf80 RCX: 00007f234808c169
RDX: 0000000000000076 RSI: 0000000000000040 RDI: 0000000020000240
RBP: 00007f23480e7ca1 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffe0919ffdf R14: 00007f2348e06300 R15: 0000000000022000
</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.

syzbot

unread,
Aug 20, 2023, 1:52:41 PM8/20/23
to syzkaller...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages