[Android 5.15] general protection fault in dir_rename_wrap

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 4edafe6c0231 Merge fd63fb84ed6d ("fs/proc: do_task_stat: m..
git tree: android13-5.15-lts
console+strace: https://syzkaller.appspot.com/x/log.txt?x=1405359d980000
kernel config: https://syzkaller.appspot.com/x/.config?x=b844863874cfdc3c
dashboard link: https://syzkaller.appspot.com/bug?extid=a2b1186a2b2f5d47c3bc
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11c2dd03980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16c6f111980000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/3b3ca2ccf616/disk-4edafe6c.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/636ab3740da3/vmlinux-4edafe6c.xz
kernel image: https://storage.googleapis.com/syzbot-assets/161f68fbebcf/bzImage-4edafe6c.xz

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

incfs: mount failed -22
general protection fault, probably for non-canonical address 0xdffffc0000000001: 0000 [#1] PREEMPT SMP KASAN
KASAN: null-ptr-deref in range [0x0000000000000008-0x000000000000000f]
CPU: 0 PID: 711 Comm: syz-executor409 Not tainted 5.15.151-syzkaller-00127-g4edafe6c0231 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/27/2024
RIP: 0010:dir_rename fs/incfs/vfs.c:1383 [inline]
RIP: 0010:dir_rename_wrap+0x256/0x720 fs/incfs/vfs.c:91
Code: 4c 8b 3c 24 e9 3e 04 00 00 e8 06 43 59 ff 31 db 4c 89 6c 24 18 48 83 c3 08 48 89 d8 48 c1 e8 03 48 b9 00 00 00 00 00 fc ff df <80> 3c 08 00 74 08 48 89 df e8 0c 7d 9b ff 4c 8b 2b 48 8b 5c 24 28
RSP: 0018:ffffc900014f7940 EFLAGS: 00010202
RAX: 0000000000000001 RBX: 0000000000000008 RCX: dffffc0000000000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc900014f7a70 R08: ffffffff8216fe3d R09: fffff5200029ef19
R10: 0000000000000000 R11: dffffc0000000001 R12: 1ffff11022f18f03
R13: 1ffff11022f18f05 R14: ffff8881178c7818 R15: ffff8881178c7828
FS: 00007f374b2f86c0(0000) GS:ffff8881f7000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f374b2f9000 CR3: 000000012033d000 CR4: 00000000003506b0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
vfs_rename+0xd25/0x10e0 fs/namei.c:4832
do_renameat2+0xb28/0x1480 fs/namei.c:4985
__do_sys_renameat2 fs/namei.c:5018 [inline]
__se_sys_renameat2 fs/namei.c:5015 [inline]
__x64_sys_renameat2+0xdd/0xf0 fs/namei.c:5015
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7f374b33a7f9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 81 18 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:00007f374b2f8218 EFLAGS: 00000246 ORIG_RAX: 000000000000013c
RAX: ffffffffffffffda RBX: 00007f374b3c23c8 RCX: 00007f374b33a7f9
RDX: 0000000000000004 RSI: 0000000020000040 RDI: 0000000000000004
RBP: 00007f374b3c23c0 R08: 0000000000000002 R09: 0000000000000000
R10: 0000000020000080 R11: 0000000000000246 R12: 00007f374b38f0c4
R13: 0031656c69662f2e R14: 00007f374b38f070 R15: 676e69646e65702e
</TASK>
Modules linked in:
---[ end trace 4ceeb043596d8f82 ]---
RIP: 0010:dir_rename fs/incfs/vfs.c:1383 [inline]
RIP: 0010:dir_rename_wrap+0x256/0x720 fs/incfs/vfs.c:91
Code: 4c 8b 3c 24 e9 3e 04 00 00 e8 06 43 59 ff 31 db 4c 89 6c 24 18 48 83 c3 08 48 89 d8 48 c1 e8 03 48 b9 00 00 00 00 00 fc ff df <80> 3c 08 00 74 08 48 89 df e8 0c 7d 9b ff 4c 8b 2b 48 8b 5c 24 28
RSP: 0018:ffffc900014f7940 EFLAGS: 00010202
RAX: 0000000000000001 RBX: 0000000000000008 RCX: dffffc0000000000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc900014f7a70 R08: ffffffff8216fe3d R09: fffff5200029ef19
R10: 0000000000000000 R11: dffffc0000000001 R12: 1ffff11022f18f03
R13: 1ffff11022f18f05 R14: ffff8881178c7818 R15: ffff8881178c7828
FS: 00007f374b2f86c0(0000) GS:ffff8881f7000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f374b2f9000 CR3: 000000012033d000 CR4: 00000000003506b0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
0: 4c 8b 3c 24 mov (%rsp),%r15
4: e9 3e 04 00 00 jmp 0x447
9: e8 06 43 59 ff call 0xff594314
e: 31 db xor %ebx,%ebx
10: 4c 89 6c 24 18 mov %r13,0x18(%rsp)
15: 48 83 c3 08 add $0x8,%rbx
19: 48 89 d8 mov %rbx,%rax
1c: 48 c1 e8 03 shr $0x3,%rax
20: 48 b9 00 00 00 00 00 movabs $0xdffffc0000000000,%rcx
27: fc ff df
* 2a: 80 3c 08 00 cmpb $0x0,(%rax,%rcx,1) <-- trapping instruction
2e: 74 08 je 0x38
30: 48 89 df mov %rbx,%rdi
33: e8 0c 7d 9b ff call 0xff9b7d44
38: 4c 8b 2b mov (%rbx),%r13
3b: 48 8b 5c 24 28 mov 0x28(%rsp),%rbx


---
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 syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

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