Hello,
syzbot found the following issue on:
HEAD commit: 4915c32a ANDROID: GKI: update xml due change of SCSI_UFS_Q..
git tree: android-5.4
console output:
https://syzkaller.appspot.com/x/log.txt?x=17a11f19900000
kernel config:
https://syzkaller.appspot.com/x/.config?x=b5e85a4a81932633
dashboard link:
https://syzkaller.appspot.com/bug?extid=2325e7076a87674793be
compiler: Android (6032204 based on r370808) clang version 10.0.1 (
https://android.googlesource.com/toolchain/llvm-project 6e765c10313d15c02ab29977a82938f66742c3a9)
syz repro:
https://syzkaller.appspot.com/x/repro.syz?x=118f9fa9900000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+2325e7...@syzkaller.appspotmail.com
kernel BUG at fs/inode.c:1588!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 2812 Comm: syz-executor.0 Not tainted 5.4.61-syzkaller-00800-g4915c32a2f6b #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:iput+0x748/0x750 fs/inode.c:1588
Code: f4 ff e9 a1 fc ff ff 44 89 e1 80 e1 07 80 c1 03 38 c1 0f 8c d4 fe ff ff 4c 89 e7 e8 12 e1 f4 ff e9 c7 fe ff ff e8 98 a8 c6 ff <0f> 0b 66 0f 1f 44 00 00 55 41 57 41 56 53 48 89 f5 48 89 fb 49 bf
RSP: 0018:ffff8881d716fdb0 EFLAGS: 00010293
RAX: ffffffff817b6098 RBX: ffff8881ccfe6a58 RCX: ffff8881d8898000
RDX: 0000000000000000 RSI: 0000000000000040 RDI: 0000000000000000
RBP: 0000000000000040 R08: ffffffff817b59b1 R09: ffffed103adae1f1
R10: ffffed103adae1f1 R11: 0000000000000000 R12: 1ffff110399fcd2c
R13: ffff8881ccfe69c0 R14: dffffc0000000000 R15: ffff8881ccfe6960
FS: 00000000033e8940(0000) GS:ffff8881db800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffda91e67f0 CR3: 00000001ca12f006 CR4: 00000000001606f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
__sock_release net/socket.c:603 [inline]
sock_close+0x1b7/0x250 net/socket.c:1269
__fput+0x27d/0x6c0 fs/file_table.c:280
task_work_run+0x176/0x1a0 kernel/task_work.c:113
tracehook_notify_resume include/linux/tracehook.h:188 [inline]
exit_to_usermode_loop arch/x86/entry/common.c:163 [inline]
prepare_exit_to_usermode+0x286/0x2e0 arch/x86/entry/common.c:194
entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x416f01
Code: 75 14 b8 03 00 00 00 0f 05 48 3d 01 f0 ff ff 0f 83 04 1b 00 00 c3 48 83 ec 08 e8 0a fc ff ff 48 89 04 24 b8 03 00 00 00 0f 05 <48> 8b 3c 24 48 89 c2 e8 53 fc ff ff 48 89 d0 48 83 c4 08 48 3d 01
RSP: 002b:00007ffe3e1e8670 EFLAGS: 00000293 ORIG_RAX: 0000000000000003
RAX: 0000000000000000 RBX: 0000000000000005 RCX: 0000000000416f01
RDX: 0000000000000000 RSI: 00000000011901f8 RDI: 0000000000000004
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
R10: 00007ffe3e1e8760 R11: 0000000000000293 R12: 00000000011902f0
R13: 0000000000005c32 R14: ffffffffffffffff R15: 000000000118cfec
Modules linked in:
---[ end trace 0befb87666c6e15f ]---
RIP: 0010:iput+0x748/0x750 fs/inode.c:1588
Code: f4 ff e9 a1 fc ff ff 44 89 e1 80 e1 07 80 c1 03 38 c1 0f 8c d4 fe ff ff 4c 89 e7 e8 12 e1 f4 ff e9 c7 fe ff ff e8 98 a8 c6 ff <0f> 0b 66 0f 1f 44 00 00 55 41 57 41 56 53 48 89 f5 48 89 fb 49 bf
RSP: 0018:ffff8881d716fdb0 EFLAGS: 00010293
RAX: ffffffff817b6098 RBX: ffff8881ccfe6a58 RCX: ffff8881d8898000
RDX: 0000000000000000 RSI: 0000000000000040 RDI: 0000000000000000
RBP: 0000000000000040 R08: ffffffff817b59b1 R09: ffffed103adae1f1
R10: ffffed103adae1f1 R11: 0000000000000000 R12: 1ffff110399fcd2c
R13: ffff8881ccfe69c0 R14: dffffc0000000000 R15: ffff8881ccfe6960
FS: 00000000033e8940(0000) GS:ffff8881db900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055f7b28e38d0 CR3: 00000001ca12f006 CR4: 00000000001606e0
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