[moderation] [kernel?] BUG: unable to handle kernel paging request in save_trace

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 2668e3ae2ef3 Merge tag 'scsi-fixes' of git://git.kernel.or..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=157e44f7180000
kernel config: https://syzkaller.appspot.com/x/.config?x=85dbe39cf8e4f599
dashboard link: https://syzkaller.appspot.com/bug?extid=1165bb30dbd1ee349fcf
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
CC: [jst...@google.com linux-...@vger.kernel.org sb...@kernel.org tg...@linutronix.de]

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

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/7bc7510fe41f/non_bootable_disk-2668e3ae.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/34abd7b02871/vmlinux-2668e3ae.xz
kernel image: https://storage.googleapis.com/syzbot-assets/9a5d6a92f905/bzImage-2668e3ae.xz

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

BUG: unable to handle page fault for address: 00000000000a639e
#PF: supervisor write access in kernel mode
#PF: error_code(0x0002) - not-present page
PGD 44092067 P4D 44092067 PUD 4407a067 PMD 0
Oops: 0002 [#1] PREEMPT SMP KASAN NOPTI
CPU: 2 PID: 6404 Comm: syz-executor.2 Not tainted 6.9.0-rc4-syzkaller-00113-g2668e3ae2ef3 #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
RIP: 0010:arch_stack_walk+0xff/0x170 arch/x86/kernel/stacktrace.c:25
Code: 50 59 00 48 89 de 4c 89 f7 41 ff d5 0f 1f 00 31 ff 89 c3 89 c6 e8 71 4a 59 00 84 db 74 20 e8 e8 4f 59 00 4c 89 e7 e8 90 a3 08 <00> 8b 9d 70 ff ff ff 31 ff 89 de e8 b1 4a 59 00 85 db 75 a1 e8 c8
RSP: 0018:ffffc900035b6838 EFLAGS: 00010086
RAX: 0000000000000001 RBX: 00000000000af301 RCX: ffffc900039c1000
RDX: 0000000000040000 RSI: ffffffff813d1721 RDI: 0000000000000005
RBP: ffffc900035b68d0 R08: 0000000000000005 R09: 0000000000000000
R10: 0000000080000000 R11: 0000000000000002 R12: ffffc900035b6840
R13: ffffffff81798ac0 R14: ffffc900035b6900 R15: ffff888028cdc880
FS: 00007fb8ed7936c0(0000) GS:ffff88806b400000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000000a639e CR3: 000000001face000 CR4: 0000000000350ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
stack_trace_save+0x95/0xd0 kernel/stacktrace.c:122
save_trace+0x53/0xb50 kernel/locking/lockdep.c:582
check_prev_add kernel/locking/lockdep.c:3195 [inline]
check_prevs_add kernel/locking/lockdep.c:3253 [inline]
validate_chain kernel/locking/lockdep.c:3869 [inline]
__lock_acquire+0x2d49/0x3b30 kernel/locking/lockdep.c:5137
lock_acquire kernel/locking/lockdep.c:5754 [inline]
lock_acquire+0x1b1/0x560 kernel/locking/lockdep.c:5719
seqcount_lockdep_reader_access include/linux/seqlock.h:72 [inline]
ktime_get_coarse_real_ts64+0x18f/0x200 kernel/time/timekeeping.c:2262
current_time fs/inode.c:2499 [inline]
inode_update_timestamps+0x3df/0x560 fs/inode.c:1871
generic_update_time+0x1e/0xf0 fs/inode.c:1900
inode_update_time fs/inode.c:1920 [inline]
touch_atime+0x4ee/0x5d0 fs/inode.c:1992
file_accessed include/linux/fs.h:2459 [inline]
filemap_read+0xb2f/0xd10 mm/filemap.c:2669
generic_file_read_iter+0x350/0x460 mm/filemap.c:2782
ntfs_file_read_iter+0x258/0x330 fs/ntfs3/file.c:768
__kernel_read+0x3ec/0xb20 fs/read_write.c:434
integrity_kernel_read+0x7f/0xb0 security/integrity/iint.c:28
ima_calc_file_hash_tfm+0x2cf/0x3e0 security/integrity/ima/ima_crypto.c:485
ima_calc_file_shash security/integrity/ima/ima_crypto.c:516 [inline]
ima_calc_file_hash+0x1c6/0x4a0 security/integrity/ima/ima_crypto.c:573
ima_collect_measurement+0x7f7/0x950 security/integrity/ima/ima_api.c:291
process_measurement+0x11ae/0x2100 security/integrity/ima/ima_main.c:359
ima_file_check+0xc1/0x110 security/integrity/ima/ima_main.c:559
security_file_post_open+0x6d/0xc0 security/security.c:2981
do_open fs/namei.c:3644 [inline]
path_openat+0x17ad/0x2990 fs/namei.c:3799
do_filp_open+0x1dc/0x430 fs/namei.c:3826
do_sys_openat2+0x17a/0x1e0 fs/open.c:1406
do_sys_open fs/open.c:1421 [inline]
__do_sys_openat fs/open.c:1437 [inline]
__se_sys_openat fs/open.c:1432 [inline]
__x64_sys_openat+0x175/0x210 fs/open.c:1432
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xcf/0x260 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fb8eca7dea9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 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 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fb8ed7930c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00007fb8ecbabf80 RCX: 00007fb8eca7dea9
RDX: 0000000000000000 RSI: 0000000020000280 RDI: ffffffffffffff9c
RBP: 00007fb8ecaca4a4 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000000b R14: 00007fb8ecbabf80 R15: 00007ffd53208978
</TASK>
Modules linked in:
CR2: 00000000000a639e
---[ end trace 0000000000000000 ]---
RIP: 0010:arch_stack_walk+0xff/0x170 arch/x86/kernel/stacktrace.c:25
Code: 50 59 00 48 89 de 4c 89 f7 41 ff d5 0f 1f 00 31 ff 89 c3 89 c6 e8 71 4a 59 00 84 db 74 20 e8 e8 4f 59 00 4c 89 e7 e8 90 a3 08 <00> 8b 9d 70 ff ff ff 31 ff 89 de e8 b1 4a 59 00 85 db 75 a1 e8 c8
RSP: 0018:ffffc900035b6838 EFLAGS: 00010086
RAX: 0000000000000001 RBX: 00000000000af301 RCX: ffffc900039c1000
RDX: 0000000000040000 RSI: ffffffff813d1721 RDI: 0000000000000005
RBP: ffffc900035b68d0 R08: 0000000000000005 R09: 0000000000000000
R10: 0000000080000000 R11: 0000000000000002 R12: ffffc900035b6840
R13: ffffffff81798ac0 R14: ffffc900035b6900 R15: ffff888028cdc880
FS: 00007fb8ed7936c0(0000) GS:ffff88806b400000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000000a639e CR3: 000000001face000 CR4: 0000000000350ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


---
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