[Android 5.10] BUG: corrupted list in __dentry_kill

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: e7daca75b4c3 ANDROID: GKI: db845c: Update symbols list and..
git tree: android13-5.10-lts
console+strace: https://syzkaller.appspot.com/x/log.txt?x=133bf39e180000
kernel config: https://syzkaller.appspot.com/x/.config?x=1a6e39f6bdc97aed
dashboard link: https://syzkaller.appspot.com/bug?extid=b64ce08e31a10a8d28c6
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=133ba265180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17b88d65180000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/cec0e413e034/disk-e7daca75.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/e97d4453b5ff/vmlinux-e7daca75.xz
kernel image: https://storage.googleapis.com/syzbot-assets/3d97ddfb5394/bzImage-e7daca75.xz

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

R13: 00007ffeae1806e8 R14: 0000000000000001 R15: 0000000000000001
---[ end trace c35cd741cfec422e ]---
list_del corruption. prev->next should be ffff88811c8e55e0, but was ffff88811c8e5910
------------[ cut here ]------------
kernel BUG at lib/list_debug.c:61!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 286 Comm: syz-executor270 Tainted: G W 5.10.209-syzkaller-00001-ge7daca75b4c3 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/29/2024
RIP: 0010:__list_del_entry_valid+0x10c/0x120 lib/list_debug.c:59
Code: 4c 89 f6 e8 e5 cc 54 02 0f 0b 48 c7 c7 40 0e 60 85 4c 89 f6 e8 d4 cc 54 02 0f 0b 48 c7 c7 a0 0e 60 85 4c 89 f6 e8 c3 cc 54 02 <0f> 0b 48 c7 c7 00 0f 60 85 4c 89 f6 e8 b2 cc 54 02 0f 0b cc 55 48
RSP: 0018:ffffc90000bd7aa0 EFLAGS: 00010246
RAX: 0000000000000054 RBX: ffff88811c8e5910 RCX: 14ebe5f559437900
RDX: 0000000000000000 RSI: 0000000000000002 RDI: 0000000000000000
RBP: ffffc90000bd7ac0 R08: ffffffff81521d98 R09: fffff5200017ae6d
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: ffff88811c8e55a8 R14: ffff88811c8e55e0 R15: ffff88811c8e5d50
FS: 0000555555a44380(0000) GS:ffff8881f7100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020004b30 CR3: 000000011e700000 CR4: 00000000003506a0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
__list_del_entry include/linux/list.h:132 [inline]
dentry_unlist fs/dcache.c:522 [inline]
__dentry_kill+0x250/0x650 fs/dcache.c:575
dentry_kill+0xc0/0x2a0
dput+0x160/0x310 fs/dcache.c:878
path_put+0x39/0x60 fs/namei.c:499
dentry_release+0x52/0xb0 fs/incfs/vfs.c:1563
__dentry_kill+0x4ad/0x650 fs/dcache.c:584
dentry_kill+0xc0/0x2a0
dput+0x160/0x310 fs/dcache.c:878
do_renameat2+0x9ae/0x1130 fs/namei.c:4609
__do_sys_renameat2 fs/namei.c:4643 [inline]
__se_sys_renameat2 fs/namei.c:4640 [inline]
__x64_sys_renameat2+0xdd/0xf0 fs/namei.c:4640
do_syscall_64+0x34/0x70
entry_SYSCALL_64_after_hwframe+0x61/0xc6
RIP: 0033:0x7f2b88f22529
Code: 48 83 c4 28 c3 e8 37 17 00 00 0f 1f 80 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 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffeae180528 EFLAGS: 00000246 ORIG_RAX: 000000000000013c
RAX: ffffffffffffffda RBX: 0030656c69662f2e RCX: 00007f2b88f22529
RDX: 00000000ffffff9c RSI: 0000000020004b00 RDI: 0000000000000003
RBP: 00007f2b88f95610 R08: 0000000000000000 R09: 00007ffeae1806f8
R10: 0000000020000100 R11: 0000000000000246 R12: 0000000000000001
R13: 00007ffeae1806e8 R14: 0000000000000001 R15: 0000000000000001
Modules linked in:
---[ end trace c35cd741cfec422f ]---
RIP: 0010:__list_del_entry_valid+0x10c/0x120 lib/list_debug.c:59
Code: 4c 89 f6 e8 e5 cc 54 02 0f 0b 48 c7 c7 40 0e 60 85 4c 89 f6 e8 d4 cc 54 02 0f 0b 48 c7 c7 a0 0e 60 85 4c 89 f6 e8 c3 cc 54 02 <0f> 0b 48 c7 c7 00 0f 60 85 4c 89 f6 e8 b2 cc 54 02 0f 0b cc 55 48
RSP: 0018:ffffc90000bd7aa0 EFLAGS: 00010246
RAX: 0000000000000054 RBX: ffff88811c8e5910 RCX: 14ebe5f559437900
RDX: 0000000000000000 RSI: 0000000000000002 RDI: 0000000000000000
RBP: ffffc90000bd7ac0 R08: ffffffff81521d98 R09: fffff5200017ae6d
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: ffff88811c8e55a8 R14: ffff88811c8e55e0 R15: ffff88811c8e5d50
FS: 0000555555a44380(0000) GS:ffff8881f7100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020004b30 CR3: 000000011e700000 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.

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