kernel BUG in notify_change

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 55e9d3c6 ANDROID: GKI: add fields required to enable CONFI..
git tree: android12-5.4
console output: https://syzkaller.appspot.com/x/log.txt?x=178b05cad00000
kernel config: https://syzkaller.appspot.com/x/.config?x=3ab48ea7db7e9a3e
dashboard link: https://syzkaller.appspot.com/bug?extid=1abbb936c4754892fc19
compiler: Debian clang version 11.0.1-2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1167b646d00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=142111b0d00000

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

------------[ cut here ]------------
kernel BUG at fs/attr.c:289!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 333 Comm: syz-executor154 Not tainted 5.4.101-syzkaller-00440-g55e9d3c6b5f7 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:notify_change+0xeff/0xf10 fs/attr.c:289
Code: fa f4 ff e9 71 f6 ff ff 44 89 f9 80 e1 07 fe c1 38 c1 0f 8c 2b fd ff ff 4c 89 ff e8 cb fa f4 ff e9 1e fd ff ff e8 41 37 c6 ff <0f> 0b 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 be 01 00 00 00
RSP: 0018:ffff8881e8c17b28 EFLAGS: 00010293
RAX: ffffffff819ec51f RBX: 0000000000000001 RCX: ffff8881e8d02f40
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000
RBP: 00000000326e0460 R08: ffffffff819ebb9a R09: ffff8881e8c17aa0
R10: ffffed103d182f56 R11: 0000000000000000 R12: dffffc0000000000
R13: ffff8881efa48880 R14: ffff8881e8c17d60 R15: 0000000000001847
FS: 00000000012e03c0(0000) GS:ffff8881f6f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00005599899c47c8 CR3: 00000001df65f000 CR4: 00000000001406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
incfs_setattr+0x1dc/0x350 fs/incfs/vfs.c:1424
notify_change+0xb18/0xf10 fs/attr.c:336
chown_common+0x3a1/0x660 fs/open.c:652
do_fchownat+0x165/0x240 fs/open.c:682
__do_sys_lchown fs/open.c:707 [inline]
__se_sys_lchown fs/open.c:705 [inline]
__x64_sys_lchown+0x81/0x90 fs/open.c:705
do_syscall_64+0xcb/0x150 arch/x86/entry/common.c:290
entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x443a69
Code: 28 c3 e8 5a 14 00 00 66 2e 0f 1f 84 00 00 00 00 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 c4 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffe3abfd8d8 EFLAGS: 00000246 ORIG_RAX: 000000000000005e
RAX: ffffffffffffffda RBX: 00007ffe3abfd8e8 RCX: 0000000000443a69
RDX: 000000000000ee00 RSI: 000000000000ee01 RDI: 0000000020000240
RBP: 00007ffe3abfd8e0 R08: 0000000000401fd0 R09: 0000000000401fd0
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00000000004b1018 R15: 00000000004004a0
Modules linked in:
---[ end trace 98530eb4d4bde13d ]---
RIP: 0010:notify_change+0xeff/0xf10 fs/attr.c:289
Code: fa f4 ff e9 71 f6 ff ff 44 89 f9 80 e1 07 fe c1 38 c1 0f 8c 2b fd ff ff 4c 89 ff e8 cb fa f4 ff e9 1e fd ff ff e8 41 37 c6 ff <0f> 0b 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 be 01 00 00 00
RSP: 0018:ffff8881e8c17b28 EFLAGS: 00010293
RAX: ffffffff819ec51f RBX: 0000000000000001 RCX: ffff8881e8d02f40
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000
RBP: 00000000326e0460 R08: ffffffff819ebb9a R09: ffff8881e8c17aa0
R10: ffffed103d182f56 R11: 0000000000000000 R12: dffffc0000000000
R13: ffff8881efa48880 R14: ffff8881e8c17d60 R15: 0000000000001847
FS: 00000000012e03c0(0000) GS:ffff8881f6f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00005599899831b0 CR3: 00000001df65f000 CR4: 00000000001406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


---
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.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches