Hello,
syzbot found the following issue on:
HEAD commit: 993bed180178 Merge "Merge branch 'android13-5.15' into bra..
git tree: android13-5.15-lts
console+strace:
https://syzkaller.appspot.com/x/log.txt?x=1251b6d3180000
kernel config:
https://syzkaller.appspot.com/x/.config?x=49ce29477ba81e8f
dashboard link:
https://syzkaller.appspot.com/bug?extid=6807813924e95a9e0a09
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=167ee33d180000
C reproducer:
https://syzkaller.appspot.com/x/repro.c?x=1166968d180000
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/4098d24d4c8b/disk-993bed18.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/94fbc07ac02d/vmlinux-993bed18.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/eed14de06c19/bzImage-993bed18.xz
mounted in repro:
https://storage.googleapis.com/syzbot-assets/88814c3a9128/mount_0.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+680781...@syzkaller.appspotmail.com
EXT4-fs (loop0): mounted filesystem without journal. Opts: nobarrier,noblock_validity,nogrpid,bh,max_batch_time=0x0000000000000400,resgid=0x0000000000000000,jqfmt=vfsold,i_version,resgid=0x0000000000000000,errors=continue. Quota mode: writeback.
------------[ cut here ]------------
kernel BUG at fs/namei.c:2933!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 295 Comm: syz-executor345 Not tainted 5.15.148-syzkaller-00718-g993bed180178 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
RIP: 0010:may_delete+0x6eb/0x6f0 fs/namei.c:2933
Code: 44 89 e1 80 e1 07 80 c1 03 38 c1 0f 8c 7f fe ff ff 4c 89 e7 e8 e6 77 f4 ff e9 72 fe ff ff e8 5c 67 b2 ff 0f 0b e8 55 67 b2 ff <0f> 0b 0f 1f 00 55 48 89 e5 41 56 53 48 89 fb e8 41 67 b2 ff 4c 8d
RSP: 0018:ffffc90000987b10 EFLAGS: 00010293
RAX: ffffffff81bdba2b RBX: ffff88811b97c7a0 RCX: ffff88811e23a780
RDX: 0000000000000000 RSI: 0000000000200000 RDI: 0000000000000000
RBP: ffffc90000987b78 R08: ffffffff81bdb3bf R09: 0000000000000003
R10: fffff52000130f44 R11: dffffc0000000001 R12: ffff88811b97cdd0
R13: 1ffff1102372f9ba R14: ffff88810fe2c1a0 R15: dffffc0000000000
FS: 0000000000000000(0000) GS:ffff8881f7100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f66e84b9130 CR3: 000000010c44e000 CR4: 00000000003506a0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
vfs_rmdir+0x32/0x470 fs/namei.c:4136
incfs_kill_sb+0x113/0x230 fs/incfs/vfs.c:1961
deactivate_locked_super+0xad/0x110 fs/super.c:335
deactivate_super+0xbe/0xf0 fs/super.c:366
cleanup_mnt+0x45c/0x510 fs/namespace.c:1143
__cleanup_mnt+0x19/0x20 fs/namespace.c:1150
task_work_run+0x129/0x190 kernel/task_work.c:164
exit_task_work include/linux/task_work.h:32 [inline]
do_exit+0xc48/0x2ca0 kernel/exit.c:878
do_group_exit+0x141/0x310 kernel/exit.c:1000
__do_sys_exit_group kernel/exit.c:1011 [inline]
__se_sys_exit_group kernel/exit.c:1009 [inline]
__x64_sys_exit_group+0x3f/0x40 kernel/exit.c:1009
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:0x7f66e843eac9
Code: Unable to access opcode bytes at RIP 0x7f66e843ea9f.
RSP: 002b:00007ffc92f439b8 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 0000000000000001 RCX: 00007f66e843eac9
RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000001
RBP: 00007f66e84bb370 R08: ffffffffffffffb8 R09: 00007ffc92f43a90
R10: 0000000000000e01 R11: 0000000000000246 R12: 00007f66e84bb370
R13: 0000000000000000 R14: 00007f66e84bc0e0 R15: 00007f66e840cd80
</TASK>
Modules linked in:
---[ end trace 7182e86c755b0f0b ]---
RIP: 0010:may_delete+0x6eb/0x6f0 fs/namei.c:2933
Code: 44 89 e1 80 e1 07 80 c1 03 38 c1 0f 8c 7f fe ff ff 4c 89 e7 e8 e6 77 f4 ff e9 72 fe ff ff e8 5c 67 b2 ff 0f 0b e8 55 67 b2 ff <0f> 0b 0f 1f 00 55 48 89 e5 41 56 53 48 89 fb e8 41 67 b2 ff 4c 8d
RSP: 0018:ffffc90000987b10 EFLAGS: 00010293
RAX: ffffffff81bdba2b RBX: ffff88811b97c7a0 RCX: ffff88811e23a780
RDX: 0000000000000000 RSI: 0000000000200000 RDI: 0000000000000000
RBP: ffffc90000987b78 R08: ffffffff81bdb3bf R09: 0000000000000003
R10: fffff52000130f44 R11: dffffc0000000001 R12: ffff88811b97cdd0
R13: 1ffff1102372f9ba R14: ffff88810fe2c1a0 R15: dffffc0000000000
FS: 0000000000000000(0000) GS:ffff8881f7000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00005576b3af6228 CR3: 000000011dfce000 CR4: 00000000003506b0
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