[moderation] [fs?] linux-next test error: WARNING in __debugfs_file_get

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 2b88851f583d Add linux-next specific files for 20250110
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1542ccb0580000
kernel config: https://syzkaller.appspot.com/x/.config?x=2c9d32675cb8d2a5
dashboard link: https://syzkaller.appspot.com/bug?extid=514e1fef214597317302
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
CC: [da...@kernel.org gre...@linuxfoundation.org linux-...@vger.kernel.org linux-...@vger.kernel.org linux...@vger.kernel.org raf...@kernel.org s...@canb.auug.org.au]

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/5e0fc155a429/disk-2b88851f.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/4c385070961a/vmlinux-2b88851f.xz
kernel image: https://storage.googleapis.com/syzbot-assets/93d17a01788a/bzImage-2b88851f.xz

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

------------[ cut here ]------------
WARNING: CPU: 1 PID: 5822 at fs/debugfs/file.c:90 __debugfs_file_get+0x5e3/0x6f0 fs/debugfs/file.c:90
Modules linked in:
CPU: 1 UID: 0 PID: 5822 Comm: syz-executor Not tainted 6.13.0-rc6-next-20250110-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
RIP: 0010:__debugfs_file_get+0x5e3/0x6f0 fs/debugfs/file.c:90
Code: 3f 01 48 b8 00 00 00 00 00 fc ff df 41 0f b6 44 05 00 84 c0 0f 85 e9 00 00 00 44 8b 74 24 40 e9 4f ff ff ff e8 2e 90 19 fe 90 <0f> 0b 90 b8 ea ff ff ff 4c 8b 3c 24 e9 5c ff ff ff 44 89 e9 80 e1
RSP: 0018:ffffc9000404f720 EFLAGS: 00010293
RAX: ffffffff83a5b0b2 RBX: 1ffff11029187e4a RCX: ffff88807df60000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc9000404f7d0 R08: ffffffff83a5abc7 R09: ffffffff8235b45d
R10: 0000000000000002 R11: ffffffff83a5b7b0 R12: 0000000000000000
R13: ffff888148c3f250 R14: dffffc0000000000 R15: ffffffff8c47e761
FS: 000055556d010500(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fd3711e34c8 CR3: 000000007e2b2000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
debugfs_file_get fs/debugfs/file.c:152 [inline]
open_proxy_open+0x4f/0x4c0 fs/debugfs/file.c:283
do_dentry_open+0xdec/0x1960 fs/open.c:955
vfs_open+0x3b/0x370 fs/open.c:1085
do_open fs/namei.c:3828 [inline]
path_openat+0x2c74/0x3580 fs/namei.c:3987
do_filp_open+0x27f/0x4e0 fs/namei.c:4014
do_sys_openat2+0x13e/0x1d0 fs/open.c:1427
do_sys_open fs/open.c:1442 [inline]
__do_sys_openat fs/open.c:1458 [inline]
__se_sys_openat fs/open.c:1453 [inline]
__x64_sys_openat+0x247/0x2a0 fs/open.c:1453
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fd371184611
Code: 75 57 89 f0 25 00 00 41 00 3d 00 00 41 00 74 49 80 3d 3a 7f 1c 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:00007ffec788e0b0 EFLAGS: 00000202 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 0000000000080001 RCX: 00007fd371184611
RDX: 0000000000080001 RSI: 00007fd3711e34c8 RDI: 00000000ffffff9c
RBP: 00007fd3711e34c8 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000202 R12: 000000000000000b
R13: 00007ffec788e150 R14: 00007fd371201a6d R15: 000055556d02a010
</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]

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