[moderation] [fs?] WARNING in debugfs_file_get

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 1b8af6552cb7 Merge tag 'powerpc-6.7-3' of git://git.kernel..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1542d59ae80000
kernel config: https://syzkaller.appspot.com/x/.config?x=feecd5c0a180f4a8
dashboard link: https://syzkaller.appspot.com/bug?extid=e3f2df3bd1dec80ac9ea
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
CC: [gre...@linuxfoundation.org linux-...@vger.kernel.org linux-...@vger.kernel.org raf...@kernel.org]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/ed27b1d6945e/disk-1b8af655.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/43d297d9a364/vmlinux-1b8af655.xz
kernel image: https://storage.googleapis.com/syzbot-assets/e734d6d673d8/bzImage-1b8af655.xz

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

------------[ cut here ]------------
WARNING: CPU: 0 PID: 5084 at kernel/locking/lockdep.c:1226 lockdep_register_key+0xcd/0x200 kernel/locking/lockdep.c:1226
Modules linked in:
CPU: 0 PID: 5084 Comm: syz-executor.0 Not tainted 6.7.0-rc3-syzkaller-00298-g1b8af6552cb7 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/10/2023
RIP: 0010:lockdep_register_key+0xcd/0x200 kernel/locking/lockdep.c:1226
Code: 00 00 00 00 00 fc ff df eb 1a 48 89 d8 48 c1 e8 03 42 80 3c 38 00 0f 85 fa 00 00 00 48 8b 1b 48 85 db 74 2e 48 39 eb 75 e1 90 <0f> 0b 90 e8 bb f7 ff ff 9c 58 f6 c4 02 0f 85 be 00 00 00 41 f7 c6
RSP: 0018:ffffc900034cf958 EFLAGS: 00010046
RAX: dffffc0000000000 RBX: ffff8880791ce890 RCX: 1ffffffff1e31487
RDX: 1ffffffff241608f RSI: 0000000000000004 RDI: ffffc900034cf908
RBP: ffff8880791ce890 R08: 0000000000000001 R09: fffff52000699f21
R10: 0000000000000003 R11: 0000000000000000 R12: 000000000000001f
R13: ffffffff920b0478 R14: 0000000000000202 R15: dffffc0000000000
FS: 0000555555c4f480(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f878c998008 CR3: 000000001c5e2000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
debugfs_file_get+0x40a/0x620 fs/debugfs/file.c:113
open_proxy_open+0x50/0x3f0 fs/debugfs/file.c:269
do_dentry_open+0x8d6/0x18c0 fs/open.c:948
do_open fs/namei.c:3622 [inline]
path_openat+0x1e5a/0x2c50 fs/namei.c:3779
do_filp_open+0x1de/0x430 fs/namei.c:3809
do_sys_openat2+0x176/0x1e0 fs/open.c:1440
do_sys_open fs/open.c:1455 [inline]
__do_sys_openat fs/open.c:1471 [inline]
__se_sys_openat fs/open.c:1466 [inline]
__x64_sys_openat+0x175/0x210 fs/open.c:1466
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x40/0x110 arch/x86/entry/common.c:82
entry_SYSCALL_64_after_hwframe+0x63/0x6b
RIP: 0033:0x7fd707a7b661
Code: 75 57 89 f0 25 00 00 41 00 3d 00 00 41 00 74 49 80 3d aa 08 10 00 00 74 6d 89 da 48 89 ee bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 0f 87 93 00 00 00 48 8b 54 24 28 64 48 2b 14 25
RSP: 002b:00007ffcf2f9bc20 EFLAGS: 00000202 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 0000000000000002 RCX: 00007fd707a7b661
RDX: 0000000000000002 RSI: 00007fd707ac7551 RDI: 00000000ffffff9c
RBP: 00007fd707ac7551 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000202 R12: 00007ffcf2f9c378
R13: 0000000000000003 R14: 00007fd707b9c018 R15: 0000000000000000
</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 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]

For archival purposes, forwarding an incoming command email to
syzkaller-upst...@googlegroups.com.

***

Subject: WARNING in debugfs_file_get
Author: penguin...@i-love.sakura.ne.jp

#syz fix: Revert "debugfs: annotate debugfs handlers vs. removal with lockdep"