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

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: e406d57be7bd Merge tag 'mm-nonmm-stable-2025-10-02-15-29' ..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=148565cd980000
kernel config: https://syzkaller.appspot.com/x/.config?x=43597f207a2d705
dashboard link: https://syzkaller.appspot.com/bug?extid=5d6d822cf11a81cab2b3
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.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/53aa926ccb28/disk-e406d57b.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/1616ddf1ba7b/vmlinux-e406d57b.xz
kernel image: https://storage.googleapis.com/syzbot-assets/cc076f84054d/bzImage-e406d57b.xz

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

------------[ cut here ]------------
WARNING: CPU: 1 PID: 12676 at fs/attr.c:435 notify_change+0xb99/0xe60 fs/attr.c:435
Modules linked in:
CPU: 1 UID: 0 PID: 12676 Comm: syz.3.979 Not tainted syzkaller #0 PREEMPT_{RT,(full)}
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025
RIP: 0010:notify_change+0xb99/0xe60 fs/attr.c:435
Code: 89 ff 4c 89 ee 89 ea e8 b5 9a f9 01 31 db 89 d8 48 83 c4 48 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc cc e8 48 c8 89 ff 90 <0f> 0b 90 e9 2f f5 ff ff 89 f9 80 e1 07 fe c1 38 c1 0f 8c b9 f4 ff
RSP: 0018:ffffc9000fa5fc00 EFLAGS: 00010293
RAX: ffffffff82336f78 RBX: 0000000080000000 RCX: ffff88802a635a00
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000046 R08: 0000000000000000 R09: 0000000000000000
R10: dffffc0000000000 R11: ffffed10079ae34c R12: ffffc9000fa5fd20
R13: ffff88805af08f78 R14: dffffc0000000000 R15: ffffffff8d4fd9a0
FS: 00007f05014cd6c0(0000) GS:ffff88812713b000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fad6ad21000 CR3: 00000000380ae000 CR4: 00000000003526f0
Call Trace:
<TASK>
chown_common+0x40c/0x5c0 fs/open.c:791
do_fchownat+0x161/0x270 fs/open.c:822
__do_sys_chown fs/open.c:842 [inline]
__se_sys_chown fs/open.c:840 [inline]
__x64_sys_chown+0x82/0xa0 fs/open.c:840
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f050328eec9
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:00007f05014cd038 EFLAGS: 00000246 ORIG_RAX: 000000000000005c
RAX: ffffffffffffffda RBX: 00007f05034e6090 RCX: 00007f050328eec9
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000200000000080
RBP: 00007f0503311f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f05034e6128 R14: 00007f05034e6090 R15: 00007ffcf912be88
</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