[v6.1] WARNING in notify_change

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 347385861c50 Linux 6.1.84
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=16d69bd3180000
kernel config: https://syzkaller.appspot.com/x/.config?x=40dfd13b04bfc094
dashboard link: https://syzkaller.appspot.com/bug?extid=c291b6d61bc0f5c8615c
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/73d2a8622b6e/disk-34738586.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/e7bc2e0101a7/vmlinux-34738586.xz
kernel image: https://storage.googleapis.com/syzbot-assets/7b96d1168608/bzImage-34738586.xz

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

------------[ cut here ]------------
WARNING: CPU: 0 PID: 11110 at fs/attr.c:390 notify_change+0xd61/0xfc0
Modules linked in:
CPU: 0 PID: 11110 Comm: syz-executor.3 Not tainted 6.1.84-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
RIP: 0010:notify_change+0xd61/0xfc0 fs/attr.c:390
Code: e6 e8 e3 a1 05 02 4c 89 e7 89 de e8 79 e5 05 02 45 31 f6 44 89 f0 48 83 c4 58 5b 41 5c 41 5d 41 5e 41 5f 5d c3 e8 cf c4 91 ff <0f> 0b e9 66 f3 ff ff 44 89 f1 80 e1 07 fe c1 38 c1 0f 8c e9 f2 ff
RSP: 0018:ffffc9000ed67c10 EFLAGS: 00010283
RAX: ffffffff81f8c221 RBX: 0000000000000000 RCX: 0000000000040000
RDX: ffffc900049a8000 RSI: 0000000000004ac0 RDI: 0000000000004ac1
RBP: ffffffff8cfd4ea0 R08: ffffffff81f8b580 R09: ffffed100b1702a2
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: ffff888050cfb1a0 R14: ffff888058b81428 R15: ffffc9000ed67d60
FS: 00007f19cd95b6c0(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f19cd95bd58 CR3: 000000007ab1c000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
chown_common+0x5aa/0x900 fs/open.c:736
do_fchownat+0x169/0x240 fs/open.c:767
__do_sys_lchown fs/open.c:792 [inline]
__se_sys_lchown fs/open.c:790 [inline]
__x64_sys_lchown+0x81/0x90 fs/open.c:790
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f19ccc7de69
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 00 00 90 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 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f19cd95b0c8 EFLAGS: 00000246 ORIG_RAX: 000000000000005e
RAX: ffffffffffffffda RBX: 00007f19ccdac050 RCX: 00007f19ccc7de69
RDX: 0000000000000000 RSI: ffffffffffffffff RDI: 0000000020000100
RBP: 00007f19cccca47a R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000006e R14: 00007f19ccdac050 R15: 00007ffe179211f8
</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