[syzbot] [jfs] WARNING in file_remove_privs_flags

[syzbot <syzbot+11df51d643e254ef16bb@syzkaller.appspotmail.com>]

Hello,

syzbot found the following issue on:

HEAD commit:    32c52ec87d62 x86/insn-eval: Fix shadowed segment index in ..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1308b20d580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=b38d39c45202f4fa
dashboard link: https://syzkaller.appspot.com/bug?extid=11df51d643e254ef16bb
compiler:       Debian clang version 22.1.8 (1~deb13u4), Debian LLD 22.1.8

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/77ec099385a8/disk-32c52ec8.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f5adfb921648/vmlinux-32c52ec8.xz
kernel image: https://storage.googleapis.com/syzbot-assets/65b38cab4ac2/bzImage-32c52ec8.xz

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

------------[ cut here ]------------
d_inode(dentry) != file_inode(file)
WARNING: ./include/linux/fs.h:1363 at file_dentry include/linux/fs.h:1363 [inline], CPU#1: kworker/u8:2/48
WARNING: ./include/linux/fs.h:1363 at file_remove_privs_flags+0x556/0x610 fs/inode.c:2373, CPU#1: kworker/u8:2/48
Modules linked in:
CPU: 1 UID: 0 PID: 48 Comm: kworker/u8:2 Not tainted syzkaller #0 PREEMPT_{RT,(full)} 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
Workqueue: loop0 loop_workfn
RIP: 0010:file_dentry include/linux/fs.h:1363 [inline]
RIP: 0010:file_remove_privs_flags+0x556/0x610 fs/inode.c:2373
Code: 00 75 4d 44 89 e8 48 8d 65 d8 5b 41 5c 41 5d 41 5e 41 5f 5d e9 1b 61 13 09 cc e8 75 d0 7b ff e9 a5 fe ff ff e8 6b d0 7b ff 90 <0f> 0b 90 e9 b0 fb ff ff 44 89 e9 80 e1 07 80 c1 03 38 c1 0f 8c d9
RSP: 0018:ffffc90000ba7480 EFLAGS: 00010293
RAX: ffffffff824b0995 RBX: ffff8880317652a0 RCX: ffff88801e689f40
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc90000ba75d8 R08: 0000000000000000 R09: 0000000000000000
R10: dffffc0000000000 R11: fffffbfff2164770 R12: 0000000000000000
R13: 1ffff110062eca54 R14: 1ffff11007ff35fc R15: 1ffff92000174e9c
FS:  0000000000000000(0000) GS:ffff888124abb000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffc491220d8 CR3: 0000000043560000 CR4: 00000000003526f0
Call Trace:
 <TASK>
 shmem_file_write_iter+0xaa/0x120 mm/shmem.c:3437
 lo_rw_aio+0xc78/0xf30 include/linux/percpu-rwsem.h:-1
 do_req_filebacked drivers/block/loop.c:430 [inline]
 loop_handle_cmd drivers/block/loop.c:1949 [inline]
 loop_process_work+0x638/0x11d0 drivers/block/loop.c:1984
 process_one_work kernel/workqueue.c:3396 [inline]
 process_scheduled_works+0xc3d/0x1630 kernel/workqueue.c:3479
 worker_thread+0xa47/0xfb0 kernel/workqueue.c:3560
 kthread+0x38b/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 syzkaller@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