[Android 5.15] kernel BUG in may_delete
2 views
Skip to first unread message
syzbot
Apr 3, 2024, 7:06:31 PMApr 3
to syzkaller-a...@googlegroups.com
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
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
syzbot
Apr 3, 2024, 7:36:25 PMApr 3
to syzkaller-a...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: d0d34dcb02cc FROMLIST: binder: check offset alignment in b..
syzbot found the following issue on:
git tree: android12-5.4
console+strace: https://syzkaller.appspot.com/x/log.txt?x=17768475180000
kernel config: https://syzkaller.appspot.com/x/.config?x=60c0e8be982a03fd
dashboard link: https://syzkaller.appspot.com/bug?extid=57e7210b330363b093cb
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=161ceaf6180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13f5b58d180000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/de032a90cf4e/disk-d0d34dcb.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f2bae6132625/vmlinux-d0d34dcb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/2c3043eb62d8/bzImage-d0d34dcb.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/f2f74d5bbf1e/mount_0.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
EXT4-fs (loop0): 1 truncate cleaned up
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
------------[ cut here ]------------
kernel BUG at fs/namei.c:2894!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 357 Comm: syz-executor109 Not tainted 5.4.268-syzkaller-00012-gd0d34dcb02cc #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
RIP: 0010:may_delete+0x750/0x760 fs/namei.c:2894
Code: 44 89 e1 80 e1 07 80 c1 03 38 c1 0f 8c e8 fd ff ff 4c 89 e7 e8 71 13 f6 ff e9 db fd ff ff e8 87 3f c6 ff 0f 0b e8 80 3f c6 ff <0f> 0b 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 41 56 53 48 89 fb
RSP: 0018:ffff8881db807a68 EFLAGS: 00010293
RAX: ffffffff819e07a0 RBX: ffff8881dc02fab8 RCX: ffff8881dbfa0fc0
RDX: 0000000000000000 RSI: 0000000000200000 RDI: 0000000000000000
RBP: ffff8881e8381250 R08: ffffffff819e00c8 R09: 0000000000000003
R10: ffffffffffffffff R11: dffffc0000000001 R12: ffff8881dc02faa0
R13: dffffc0000000000 R14: 0000000000000001 R15: ffff8881dc034b50
FS: 00005555560e4380(0000) GS:ffff8881f6f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f8dc5dea130 CR3: 0000000005e0e000 CR4: 00000000003406a0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
vfs_rmdir+0x29/0x3c0 fs/namei.c:3960
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
incfs_kill_sb+0x105/0x200 fs/incfs/vfs.c:1944
deactivate_locked_super+0xa8/0x110 fs/super.c:335
deactivate_super+0x1e2/0x2a0 fs/super.c:366
cleanup_mnt+0x44e/0x500 fs/namespace.c:1102
task_work_run+0x140/0x170 kernel/task_work.c:113
exit_task_work include/linux/task_work.h:22 [inline]
do_exit+0xcaf/0x2bc0 kernel/exit.c:859
do_group_exit+0x138/0x300 kernel/exit.c:982
__do_sys_exit_group kernel/exit.c:993 [inline]
__se_sys_exit_group kernel/exit.c:991 [inline]
__x64_sys_exit_group+0x3b/0x40 kernel/exit.c:991
do_syscall_64+0xca/0x1c0 arch/x86/entry/common.c:290
entry_SYSCALL_64_after_hwframe+0x5c/0xc1
Modules linked in:
---[ end trace f753f506d0b6ed4f ]---
RIP: 0010:may_delete+0x750/0x760 fs/namei.c:2894
Code: 44 89 e1 80 e1 07 80 c1 03 38 c1 0f 8c e8 fd ff ff 4c 89 e7 e8 71 13 f6 ff e9 db fd ff ff e8 87 3f c6 ff 0f 0b e8 80 3f c6 ff <0f> 0b 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 41 56 53 48 89 fb
RSP: 0018:ffff8881db807a68 EFLAGS: 00010293
RAX: ffffffff819e07a0 RBX: ffff8881dc02fab8 RCX: ffff8881dbfa0fc0
RDX: 0000000000000000 RSI: 0000000000200000 RDI: 0000000000000000
RBP: ffff8881e8381250 R08: ffffffff819e00c8 R09: 0000000000000003
R10: ffffffffffffffff R11: dffffc0000000001 R12: ffff8881dc02faa0
R13: dffffc0000000000 R14: 0000000000000001 R15: ffff8881dc034b50
FS: 00005555560e4380(0000) GS:ffff8881f6f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f8dc5dea130 CR3: 00000001e4e7b000 CR4: 00000000003406a0
syzbot
Apr 3, 2024, 7:51:29 PMApr 3
to syzkaller-a...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: af361f9a1066 UPSTREAM: usb: typec: Return size of buffer i..
syzbot found the following issue on:
git tree: android14-6.1
console+strace: https://syzkaller.appspot.com/x/log.txt?x=15611489180000
kernel config: https://syzkaller.appspot.com/x/.config?x=7bd1a415c6de5d9d
dashboard link: https://syzkaller.appspot.com/bug?extid=292d0e141b92a314ddec
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=150db58d180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=161b8139180000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/db7f428f19ce/disk-af361f9a.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f1e9b109bbcc/vmlinux-af361f9a.xz
kernel image: https://storage.googleapis.com/syzbot-assets/c386b5dd8141/bzImage-af361f9a.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/739319ce9970/mount_0.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
EXT4-fs (loop0): mounted filesystem without journal. Quota mode: writeback.
------------[ cut here ]------------
kernel BUG at fs/namei.c:2956!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 296 Comm: syz-executor304 Not tainted 6.1.75-syzkaller-00112-gaf361f9a1066 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
RIP: 0010:may_delete+0x6eb/0x6f0 fs/namei.c:2956
Code: 44 89 e1 80 e1 07 80 c1 03 38 c1 0f 8c 7f fe ff ff 4c 89 e7 e8 46 af f3 ff e9 72 fe ff ff e8 0c d4 ac ff 0f 0b e8 05 d4 ac ff <0f> 0b 0f 1f 00 55 48 89 e5 41 56 53 48 89 fb e8 f1 d3 ac ff 4c 8d
RSP: 0018:ffffc90000e37a58 EFLAGS: 00010293
RAX: ffffffff81c888cb RBX: ffff88811f11e360 RCX: ffff888109638000
RDX: 0000000000000000 RSI: 0000000000200000 RDI: 0000000000000000
RBP: ffffc90000e37ac0 R08: ffffffff81c8825f R09: 0000000000000003
R10: ffffffffffffffff R11: dffffc0000000001 R12: ffff88811f122110
R13: 1ffff11023e24422 R14: ffff888100558168 R15: dffffc0000000000
FS: 0000000000000000(0000) GS:ffff8881f7100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000555b9d759068 CR3: 000000010e9cc000 CR4: 00000000003506a0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
vfs_rmdir+0x32/0x500 fs/namei.c:4178
incfs_kill_sb+0x113/0x230 fs/incfs/vfs.c:1962
deactivate_locked_super+0xad/0x110 fs/super.c:334
deactivate_super+0xbe/0xf0 fs/super.c:365
cleanup_mnt+0x485/0x510 fs/namespace.c:1186
__cleanup_mnt+0x19/0x20 fs/namespace.c:1193
task_work_run+0x24d/0x2e0 kernel/task_work.c:179
exit_task_work include/linux/task_work.h:38 [inline]
do_exit+0xbd5/0x2b80 kernel/exit.c:875
do_group_exit+0x21a/0x2d0 kernel/exit.c:1025
__do_sys_exit_group kernel/exit.c:1036 [inline]
__se_sys_exit_group kernel/exit.c:1034 [inline]
__x64_sys_exit_group+0x3f/0x40 kernel/exit.c:1034
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fb7744c2ac9
Code: Unable to access opcode bytes at 0x7fb7744c2a9f.
RSP: 002b:00007ffc49ab3cf8 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 0000000000000001 RCX: 00007fb7744c2ac9
RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000001
RBP: 00007fb77453f370 R08: ffffffffffffffb8 R09: 00007ffc49ab3dd0
R10: 0000000000000e01 R11: 0000000000000246 R12: 00007fb77453f370
R13: 0000000000000000 R14: 00007fb7745400e0 R15: 00007fb774490d80
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:may_delete+0x6eb/0x6f0 fs/namei.c:2956
Code: 44 89 e1 80 e1 07 80 c1 03 38 c1 0f 8c 7f fe ff ff 4c 89 e7 e8 46 af f3 ff e9 72 fe ff ff e8 0c d4 ac ff 0f 0b e8 05 d4 ac ff <0f> 0b 0f 1f 00 55 48 89 e5 41 56 53 48 89 fb e8 f1 d3 ac ff 4c 8d
RSP: 0018:ffffc90000e37a58 EFLAGS: 00010293
RAX: ffffffff81c888cb RBX: ffff88811f11e360 RCX: ffff888109638000
RDX: 0000000000000000 RSI: 0000000000200000 RDI: 0000000000000000
RBP: ffffc90000e37ac0 R08: ffffffff81c8825f R09: 0000000000000003
R10: ffffffffffffffff R11: dffffc0000000001 R12: ffff88811f122110
R13: 1ffff11023e24422 R14: ffff888100558168 R15: dffffc0000000000
FS: 0000000000000000(0000) GS:ffff8881f7100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000555b9d759068 CR3: 000000010e85a000 CR4: 00000000003506a0
syzbot
Apr 3, 2024, 8:03:29 PMApr 3
to syzkaller-a...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: e7daca75b4c3 ANDROID: GKI: db845c: Update symbols list and..
syzbot found the following issue on:
git tree: android13-5.10-lts
console+strace: https://syzkaller.appspot.com/x/log.txt?x=15ff06ad180000
kernel config: https://syzkaller.appspot.com/x/.config?x=1a6e39f6bdc97aed
dashboard link: https://syzkaller.appspot.com/bug?extid=10dc2488150fe6b9673e
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=1562eea1180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13503c5e180000
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
mounted in repro: https://storage.googleapis.com/syzbot-assets/a7bd510a0286/mount_0.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
EXT4-fs (loop0): 1 truncate cleaned up
------------[ cut here ]------------
kernel BUG at fs/namei.c:2786!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 287 Comm: syz-executor210 Not tainted 5.10.209-syzkaller-00001-ge7daca75b4c3 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
RIP: 0010:may_delete+0x755/0x760 fs/namei.c:2786
Code: 44 89 e9 80 e1 07 80 c1 03 38 c1 0f 8c db fd ff ff 4c 89 ef e8 dc 37 f4 ff e9 ce fd ff ff e8 f2 be b6 ff 0f 0b e8 eb be b6 ff <0f> 0b 66 0f 1f 84 00 00 00 00 00 55 48 89 e5 41 56 53 48 89 fb e8
RSP: 0018:ffffc90000b17ad8 EFLAGS: 00010293
RAX: ffffffff81b3e905 RBX: ffff88811c4fd250 RCX: ffff88811ede4f00
RDX: 0000000000000000 RSI: 0000000000200000 RDI: 0000000000000000
RBP: ffffc90000b17b58 R08: ffffffff81b3e223 R09: 0000000000000003
R10: fffff52000162f40 R11: dffffc0000000001 R12: 0000000000000001
R13: ffff88811c4b1ee0 R14: ffff88810fda6be8 R15: dffffc0000000000
FS: 0000000000000000(0000) GS:ffff8881f7000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fc376ec0130 CR3: 000000000660f000 CR4: 00000000003506b0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
vfs_rmdir+0x2c/0x3f0 fs/namei.c:3839
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
incfs_kill_sb+0x108/0x220 fs/incfs/vfs.c:1945
deactivate_locked_super+0xad/0x110 fs/super.c:335
deactivate_super+0xbe/0xf0 fs/super.c:366
cleanup_mnt+0x45c/0x510 fs/namespace.c:1118
deactivate_super+0xbe/0xf0 fs/super.c:366
__cleanup_mnt+0x19/0x20 fs/namespace.c:1125
task_work_run+0x129/0x190 kernel/task_work.c:164
exit_task_work include/linux/task_work.h:32 [inline]
do_exit+0xc83/0x2a50 kernel/exit.c:861
exit_task_work include/linux/task_work.h:32 [inline]
do_group_exit+0x141/0x310 kernel/exit.c:983
__do_sys_exit_group kernel/exit.c:994 [inline]
__se_sys_exit_group kernel/exit.c:992 [inline]
__x64_sys_exit_group+0x3f/0x40 kernel/exit.c:992
do_syscall_64+0x34/0x70
entry_SYSCALL_64_after_hwframe+0x61/0xc6
RIP: 0033:0x7fc376e45ac9
Code: Unable to access opcode bytes at RIP 0x7fc376e45a9f.
RSP: 002b:00007ffc11cc00a8 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 0000000000000001 RCX: 00007fc376e45ac9
RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000001
RBP: 00007fc376ec2370 R08: ffffffffffffffb8 R09: 00007ffc11cc0180
R10: 0000000000000e01 R11: 0000000000000246 R12: 00007fc376ec2370
R13: 0000000000000000 R14: 00007fc376ec30e0 R15: 00007fc376e13d80
Modules linked in:
---[ end trace 9882477244f21830 ]---
RIP: 0010:may_delete+0x755/0x760 fs/namei.c:2786
Code: 44 89 e9 80 e1 07 80 c1 03 38 c1 0f 8c db fd ff ff 4c 89 ef e8 dc 37 f4 ff e9 ce fd ff ff e8 f2 be b6 ff 0f 0b e8 eb be b6 ff <0f> 0b 66 0f 1f 84 00 00 00 00 00 55 48 89 e5 41 56 53 48 89 fb e8
RSP: 0018:ffffc90000b17ad8 EFLAGS: 00010293
RAX: ffffffff81b3e905 RBX: ffff88811c4fd250 RCX: ffff88811ede4f00
RDX: 0000000000000000 RSI: 0000000000200000 RDI: 0000000000000000
RBP: ffffc90000b17b58 R08: ffffffff81b3e223 R09: 0000000000000003
R10: fffff52000162f40 R11: dffffc0000000001 R12: 0000000000000001
R13: ffff88811c4b1ee0 R14: ffff88810fda6be8 R15: dffffc0000000000
FS: 0000000000000000(0000) GS:ffff8881f7000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fc376ec0130 CR3: 000000000660f000 CR4: 00000000003506b0
syzbot
Apr 3, 2024, 11:54:16 PMApr 3
to syzkaller-a...@googlegroups.com
Bug presence analysis results: the bug reproduces only on Android 6.1.
syzbot has run the reproducer on other relevant kernel trees and got
the following results:
android14-6.1 (commit ebcdb9dc211f) on 2024/04/04:
kernel BUG in may_delete
Report: https://syzkaller.appspot.com/x/report.txt?x=14283c5e180000
lts (commit 883d1a956208) on 2024/04/04:
Didn't crash.
upstream (commit c85af715cac0) on 2024/04/04:
Didn't crash.
More details can be found at:
https://syzkaller.appspot.com/bug?extid=292d0e141b92a314ddec
syzbot has run the reproducer on other relevant kernel trees and got
the following results:
android14-6.1 (commit ebcdb9dc211f) on 2024/04/04:
kernel BUG in may_delete
Report: https://syzkaller.appspot.com/x/report.txt?x=14283c5e180000
lts (commit 883d1a956208) on 2024/04/04:
Didn't crash.
upstream (commit c85af715cac0) on 2024/04/04:
Didn't crash.
More details can be found at:
https://syzkaller.appspot.com/bug?extid=292d0e141b92a314ddec
Reply all
Reply to author
Forward
0 new messages