[moderation] [fs?] WARNING in file_remove_privs_flags

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 917719c412c4 Merge tag 'selinux-pr-20260507' of git://git...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=15e7e56a580000
kernel config: https://syzkaller.appspot.com/x/.config?x=f2e8ebfec4636d32
dashboard link: https://syzkaller.appspot.com/bug?extid=bc273027d5643e48e5b3
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
CC: [bra...@kernel.org ja...@suse.cz linux-...@vger.kernel.org linux-...@vger.kernel.org vi...@zeniv.linux.org.uk]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/c358268ad907/disk-917719c4.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/fad7094e3994/vmlinux-917719c4.xz
kernel image: https://storage.googleapis.com/syzbot-assets/b36b667b8a48/bzImage-917719c4.xz

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

------------[ cut here ]------------
d_inode(dentry) != file_inode(file)
WARNING: ./include/linux/fs.h:1368 at file_dentry include/linux/fs.h:1368 [inline], CPU#0: kworker/u8:14/1529
WARNING: ./include/linux/fs.h:1368 at file_remove_privs_flags+0x58c/0x640 fs/inode.c:2313, CPU#0: kworker/u8:14/1529
Modules linked in:
CPU: 0 UID: 0 PID: 1529 Comm: kworker/u8:14 Not tainted syzkaller #0 PREEMPT_{RT,(full)}
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/18/2026
Workqueue: loop3 loop_workfn
RIP: 0010:file_dentry include/linux/fs.h:1368 [inline]
RIP: 0010:file_remove_privs_flags+0x58c/0x640 fs/inode.c:2313
Code: 00 75 4d 44 89 e8 48 8d 65 d8 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc cc e8 1f 82 83 ff e9 90 fe ff ff e8 15 82 83 ff 90 <0f> 0b 90 e9 85 fb ff ff 44 89 f1 80 e1 07 80 c1 03 38 c1 0f 8c b7
RSP: 0018:ffffc90006adf480 EFLAGS: 00010293
RAX: ffffffff8240f23b RBX: ffff888035ab6ca0 RCX: ffff888029b19ec0
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc90006adf5d8 R08: 0000000000000000 R09: 0000000000000000
R10: dffffc0000000000 R11: fffffbfff1f11cdf R12: ffff888041268ab8
R13: 1ffff11006b56d94 R14: 0000000000000000 R15: 1ffff1100824d157
FS: 0000000000000000(0000) GS:ffff888126176000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00005555802efa68 CR3: 000000001fbda000 CR4: 00000000003526f0
Call Trace:
<TASK>
shmem_file_write_iter+0xaa/0x120 mm/shmem.c:3472
lo_rw_aio+0xc80/0xf00 include/linux/percpu-rwsem.h:-1
do_req_filebacked drivers/block/loop.c:433 [inline]
loop_handle_cmd drivers/block/loop.c:1925 [inline]
loop_process_work+0x637/0x11b0 drivers/block/loop.c:1960
process_one_work kernel/workqueue.c:3302 [inline]
process_scheduled_works+0xb5d/0x1860 kernel/workqueue.c:3385
worker_thread+0xa53/0xfc0 kernel/workqueue.c:3466
kthread+0x388/0x470 kernel/kthread.c:436
ret_from_fork+0x514/0xb70 arch/x86/kernel/process.c:158
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
</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