[moderation] [fs?] WARNING in notify_change (6)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 92fc9636d147 Add linux-next specific files for 20240926
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=149acaa9980000
kernel config: https://syzkaller.appspot.com/x/.config?x=260eb6b0404c981b
dashboard link: https://syzkaller.appspot.com/bug?extid=51158e6615c9bc9289b0
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
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/7f8c286100cb/disk-92fc9636.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/3fd0376269e6/vmlinux-92fc9636.xz
kernel image: https://storage.googleapis.com/syzbot-assets/797bd1f42c96/bzImage-92fc9636.xz

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

------------[ cut here ]------------
WARNING: CPU: 0 PID: 8839 at fs/attr.c:426 notify_change+0xc3a/0xe90 fs/attr.c:426
Modules linked in:
CPU: 0 UID: 0 PID: 8839 Comm: syz.2.1305 Not tainted 6.11.0-next-20240926-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
RIP: 0010:notify_change+0xc3a/0xe90 fs/attr.c:426
Code: 28 4c 89 e6 89 da e8 55 3b 53 02 45 31 f6 44 89 f0 48 83 c4 60 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc e8 b7 fd 7a ff 90 <0f> 0b 90 e9 92 f4 ff ff 44 89 f1 80 e1 07 fe c1 38 c1 0f 8c 14 f4
RSP: 0018:ffffc9000ec27be8 EFLAGS: 00010283
RAX: ffffffff8219e539 RBX: 0000000000000000 RCX: 0000000000040000
RDX: ffffc90017f42000 RSI: 000000000000090f RDI: 0000000000000910
RBP: ffffffff8ea900a0 R08: ffffffff8219d9c6 R09: 1ffff1100fa487a1
R10: dffffc0000000000 R11: ffffed100fa487a2 R12: ffff8880605185e0
R13: ffffc9000ec27d40 R14: ffff88807d243c30 R15: dffffc0000000000
FS: 00007f56a8faf6c0(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b32900ff8 CR3: 000000006a562000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
chown_common+0x501/0x850 fs/open.c:793
do_fchownat+0x16a/0x240 fs/open.c:824
__do_sys_lchown fs/open.c:849 [inline]
__se_sys_lchown fs/open.c:847 [inline]
__x64_sys_lchown+0x85/0xa0 fs/open.c:847
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:0x7f56a817df39
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:00007f56a8faf038 EFLAGS: 00000246 ORIG_RAX: 000000000000005e
RAX: ffffffffffffffda RBX: 00007f56a8336058 RCX: 00007f56a817df39
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000020000000
RBP: 00007f56a81f0216 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007f56a8336058 R15: 00007ffd0c211c38
</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