[v5.15] INFO: trying to register non-static key in do_mpage_readpage

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: cc5ec8769306 Linux 5.15.196
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1608d60a580000
kernel config: https://syzkaller.appspot.com/x/.config?x=e1bb6d24ef2164eb
dashboard link: https://syzkaller.appspot.com/bug?extid=8af7ac81750008d66feb
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1021c884580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10448692580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/c71c660545b2/disk-cc5ec876.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/4f011826cca6/vmlinux-cc5ec876.xz
kernel image: https://storage.googleapis.com/syzbot-assets/8ccd1a2c3f8c/bzImage-cc5ec876.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/3782ae63086f/mount_0.gz

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

loop0: detected capacity change from 0 to 4096
ntfs3: loop0: Different NTFS' sector size (4096) and media sector size (512)
ntfs3: loop0: Mark volume as dirty due to NTFS errors
INFO: trying to register non-static key.
The code is fine but needs lockdep annotation, or maybe
you didn't initialize this object before use?
turning off the locking correctness validator.
CPU: 0 PID: 4348 Comm: syz.0.17 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
Call Trace:
<TASK>
dump_stack_lvl+0x168/0x230 lib/dump_stack.c:106
assign_lock_key+0x1e0/0x1f0 kernel/locking/lockdep.c:937
register_lock_class+0x20e/0x880 kernel/locking/lockdep.c:1250
__lock_acquire+0x160/0x7c60 kernel/locking/lockdep.c:4891
lock_acquire+0x197/0x3f0 kernel/locking/lockdep.c:5623
down_read+0x44/0x2e0 kernel/locking/rwsem.c:1498
attr_data_get_block+0x10d/0x1880 fs/ntfs3/attrib.c:831
ntfs_get_block_vbo+0x2f6/0xc60 fs/ntfs3/inode.c:591
do_mpage_readpage+0x820/0x1e30 fs/mpage.c:231
mpage_readahead+0x3a6/0x8a0 fs/mpage.c:389
read_pages+0x165/0x920 mm/readahead.c:130
page_cache_ra_unbounded+0x830/0x930 mm/readahead.c:239
page_cache_sync_readahead include/linux/pagemap.h:833 [inline]
filemap_get_pages mm/filemap.c:2551 [inline]
filemap_read+0x589/0x2480 mm/filemap.c:2634
__kernel_read+0x4eb/0x910 fs/read_write.c:443
integrity_kernel_read+0x86/0xd0 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+0x1546/0x18e0 security/integrity/ima/ima_crypto.c:573
ima_collect_measurement+0x2ef/0x760 security/integrity/ima/ima_api.c:255
process_measurement+0xfb9/0x1a10 security/integrity/ima/ima_main.c:351
ima_file_check+0xc1/0x100 security/integrity/ima/ima_main.c:533
do_open fs/namei.c:3618 [inline]
path_openat+0x2735/0x2f30 fs/namei.c:3750
do_file_open_root+0x2c8/0x680 fs/namei.c:3802
file_open_root+0x15a/0x1a0 fs/open.c:1233
do_handle_open+0x47f/0x820 fs/fhandle.c:232
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:0x7fd41f6e96c9
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:00007fffb1f17068 EFLAGS: 00000246 ORIG_RAX: 0000000000000130
RAX: ffffffffffffffda RBX: 00007fd41f93ffa0 RCX: 00007fd41f6e96c9
RDX: 0000000000000000 RSI: 0000200000000240 RDI: 0000000000000005
RBP: 00007fd41f76bf91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fd41f93ffa0 R14: 00007fd41f93ffa0 R15: 0000000000000003
</TASK>
------------[ cut here ]------------
DEBUG_RWSEMS_WARN_ON(sem->magic != sem): count = 0x100, magic = 0x0, owner = 0xffff888022df3b81, curr 0xffff888022df3b80, list not empty
WARNING: CPU: 0 PID: 4348 at kernel/locking/rwsem.c:1322 __up_read+0x4e9/0x660 kernel/locking/rwsem.c:1322
Modules linked in:
CPU: 0 PID: 4348 Comm: syz.0.17 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
RIP: 0010:__up_read+0x4e9/0x660 kernel/locking/rwsem.c:1322
Code: 48 c7 c7 e0 0f 0b 8a 48 c7 c6 00 11 0b 8a 4c 89 ea 48 8b 4c 24 08 4c 8b 04 24 4c 8b 4c 24 10 41 52 e8 db 55 43 08 48 83 c4 08 <0f> 0b e9 d5 fb ff ff c6 05 3d a5 fa 0b 01 48 89 df be 08 00 00 00
RSP: 0018:ffffc90002ebe040 EFLAGS: 00010292
RAX: d14974fefc11da00 RBX: ffff88805bd9cb00 RCX: ffff888022df3b80
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: ffffc90002ebe0f0 R08: dffffc0000000000 R09: ffffed10172067b0
R10: ffffed10172067b0 R11: 1ffff110172067af R12: ffff88805bd9cb68
R13: 0000000000000100 R14: 1ffff1100b7b396d R15: ffff88805bd9cb58
FS: 000055556289d500(0000) GS:ffff8880b9000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b30c63fff CR3: 000000001ef3c000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
attr_data_get_block+0x13c/0x1880 fs/ntfs3/attrib.c:833
ntfs_get_block_vbo+0x2f6/0xc60 fs/ntfs3/inode.c:591
do_mpage_readpage+0x820/0x1e30 fs/mpage.c:231
mpage_readahead+0x3a6/0x8a0 fs/mpage.c:389
read_pages+0x165/0x920 mm/readahead.c:130
page_cache_ra_unbounded+0x830/0x930 mm/readahead.c:239
page_cache_sync_readahead include/linux/pagemap.h:833 [inline]
filemap_get_pages mm/filemap.c:2551 [inline]
filemap_read+0x589/0x2480 mm/filemap.c:2634
__kernel_read+0x4eb/0x910 fs/read_write.c:443
integrity_kernel_read+0x86/0xd0 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+0x1546/0x18e0 security/integrity/ima/ima_crypto.c:573
ima_collect_measurement+0x2ef/0x760 security/integrity/ima/ima_api.c:255
process_measurement+0xfb9/0x1a10 security/integrity/ima/ima_main.c:351
ima_file_check+0xc1/0x100 security/integrity/ima/ima_main.c:533
do_open fs/namei.c:3618 [inline]
path_openat+0x2735/0x2f30 fs/namei.c:3750
do_file_open_root+0x2c8/0x680 fs/namei.c:3802
file_open_root+0x15a/0x1a0 fs/open.c:1233
do_handle_open+0x47f/0x820 fs/fhandle.c:232
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:0x7fd41f6e96c9
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:00007fffb1f17068 EFLAGS: 00000246 ORIG_RAX: 0000000000000130
RAX: ffffffffffffffda RBX: 00007fd41f93ffa0 RCX: 00007fd41f6e96c9
RDX: 0000000000000000 RSI: 0000200000000240 RDI: 0000000000000005
RBP: 00007fd41f76bf91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fd41f93ffa0 R14: 00007fd41f93ffa0 R15: 0000000000000003
</TASK>


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

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