[moderation] [fs?] WARNING in show_mark_fhandle (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 9e4c6c1ad9a1 Merge tag 'io_uring-6.12-20241011' of git://g..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=112b5fd0580000
kernel config: https://syzkaller.appspot.com/x/.config?x=7cd9e7e4a8a0a15b
dashboard link: https://syzkaller.appspot.com/bug?extid=36edb2116a065b146199
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
CC: [amir...@gmail.com ja...@suse.cz linux-...@vger.kernel.org linux-...@vger.kernel.org]

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

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/7feb34a89c2a/non_bootable_disk-9e4c6c1a.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/e75c6071f118/vmlinux-9e4c6c1a.xz
kernel image: https://storage.googleapis.com/syzbot-assets/20f9b24a6322/bzImage-9e4c6c1a.xz

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

------------[ cut here ]------------
Can't encode file handler for inotify: 255
WARNING: CPU: 0 PID: 5111 at fs/notify/fdinfo.c:51 show_mark_fhandle+0x2c5/0x3a0 fs/notify/fdinfo.c:51
Modules linked in:
CPU: 0 UID: 0 PID: 5111 Comm: syz.0.0 Not tainted 6.12.0-rc2-syzkaller-00260-g9e4c6c1ad9a1 #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014
RIP: 0010:show_mark_fhandle+0x2c5/0x3a0 fs/notify/fdinfo.c:51
Code: 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc e8 43 3f 6f ff c6 05 b5 08 e1 0d 01 90 48 c7 c7 20 ae 19 8c 44 89 ee e8 4c 39 30 ff 90 <0f> 0b 90 90 eb 86 48 8d 4c 24 40 80 e1 07 80 c1 03 38 c1 0f 8c e3
RSP: 0018:ffffc9000307f7e0 EFLAGS: 00010246
RAX: de5d3df5bc341200 RBX: 1ffff9200060ff1e RCX: 0000000000040000
RDX: ffffc9000b54a000 RSI: 0000000000000acb RDI: 0000000000000acc
RBP: ffffc9000307f958 R08: ffffffff8155e402 R09: fffffbfff1cf9fd8
R10: dffffc0000000000 R11: fffffbfff1cf9fd8 R12: ffff888012729940
R13: 00000000000000ff R14: 1ffff9200060ff04 R15: dffffc0000000000
FS: 00007f945cb6a6c0(0000) GS:ffff88801fc00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055bc55c71be0 CR3: 000000003b92e000 CR4: 0000000000352ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
inotify_fdinfo fs/notify/fdinfo.c:86 [inline]
show_fdinfo fs/notify/fdinfo.c:34 [inline]
inotify_show_fdinfo+0x2b0/0x4e0 fs/notify/fdinfo.c:94
seq_show+0x608/0x770 fs/proc/fd.c:68
seq_read_iter+0x43f/0xd70 fs/seq_file.c:230
seq_read+0x3a9/0x4f0 fs/seq_file.c:162
vfs_read+0x201/0xbc0 fs/read_write.c:567
ksys_read+0x183/0x2b0 fs/read_write.c:712
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:0x7f945bd7dff9
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:00007f945cb6a038 EFLAGS: 00000246 ORIG_RAX: 0000000000000000
RAX: ffffffffffffffda RBX: 00007f945bf36058 RCX: 00007f945bd7dff9
RDX: 0000000000002020 RSI: 00000000200020c0 RDI: 0000000000000007
RBP: 00007f945bdf0296 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007f945bf36058 R15: 00007fffc9f59f28
</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.