kernel BUG in notify_change (3)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: ee965fe12def Merge branch 'android12-5.10' into branch 'an..
git tree: android12-5.10-lts
console+strace: https://syzkaller.appspot.com/x/log.txt?x=1364856b080000
kernel config: https://syzkaller.appspot.com/x/.config?x=d50a6822f51376ca
dashboard link: https://syzkaller.appspot.com/bug?extid=e9053c4a1d7980b9f981
compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=112ef485080000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1608bd15080000

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

kernel BUG at fs/attr.c:289!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 371 Comm: syz-executor155 Not tainted 5.10.136-syzkaller-01853-gee965fe12def #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/22/2022
RIP: 0010:notify_change+0xe02/0xe10 fs/attr.c:289
Code: f0 ff e9 83 fb ff ff 44 89 e1 80 e1 07 80 c1 03 38 c1 0f 8c 82 f7 ff ff 4c 89 e7 e8 38 95 f0 ff e9 75 f7 ff ff e8 4e 8e b6 ff <0f> 0b 66 66 2e 0f 1f 84 00 00 00 00 00 90 55 48 89 e5 41 57 41 56
RSP: 0018:ffffc90000bc7b48 EFLAGS: 00010293
RAX: ffffffff81b637f2 RBX: 0000000000001847 RCX: ffff88811e158000
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000
RBP: ffffc90000bc7bc8 R08: ffffffff81b62f9d R09: ffffc90000bc7ac0
R10: fffff52000178f5a R11: 1ffff92000178f58 R12: ffffc90000bc7d60
R13: 0000000000000001 R14: ffff88811a555770 R15: dffffc0000000000
FS: 0000555555774300(0000) GS:ffff8881f7100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020001ac0 CR3: 000000010699f000 CR4: 00000000003506a0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
incfs_setattr+0x229/0x3a0 fs/incfs/vfs.c:1612
notify_change+0xb76/0xe10 fs/attr.c:336
chown_common+0x3a1/0x660 fs/open.c:675
do_fchownat+0x175/0x250 fs/open.c:705
__do_sys_lchown fs/open.c:730 [inline]
__se_sys_lchown fs/open.c:728 [inline]
__x64_sys_lchown+0x85/0x90 fs/open.c:728
do_syscall_64+0x34/0x70 arch/x86/entry/common.c:46
entry_SYSCALL_64_after_hwframe+0x61/0xc6
RIP: 0033:0x7ff15ebe1ba9
Code: 28 c3 e8 2a 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 c0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffd60fc9c78 EFLAGS: 00000246 ORIG_RAX: 000000000000005e
RAX: ffffffffffffffda RBX: 0030656c69662f2e RCX: 00007ff15ebe1ba9
RDX: 000000000000ee01 RSI: 0000000000000000 RDI: 0000000020001ac0
RBP: 2f30656c69662f2e R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007ff15eba5de0
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
Modules linked in:
---[ end trace 0d95c96a85df13ba ]---
RIP: 0010:notify_change+0xe02/0xe10 fs/attr.c:289
Code: f0 ff e9 83 fb ff ff 44 89 e1 80 e1 07 80 c1 03 38 c1 0f 8c 82 f7 ff ff 4c 89 e7 e8 38 95 f0 ff e9 75 f7 ff ff e8 4e 8e b6 ff <0f> 0b 66 66 2e 0f 1f 84 00 00 00 00 00 90 55 48 89 e5 41 57 41 56
RSP: 0018:ffffc90000bc7b48 EFLAGS: 00010293
RAX: ffffffff81b637f2 RBX: 0000000000001847 RCX: ffff88811e158000
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000
RBP: ffffc90000bc7bc8 R08: ffffffff81b62f9d R09: ffffc90000bc7ac0
R10: fffff52000178f5a R11: 1ffff92000178f58 R12: ffffc90000bc7d60
R13: 0000000000000001 R14: ffff88811a555770 R15: dffffc0000000000
FS: 0000555555774300(0000) GS:ffff8881f7100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020001ac0 CR3: 000000010699f000 CR4: 00000000003506a0
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