BUG: unable to handle kernel paging request in syscall_trace_enter

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 2e929716 FROMGIT: scsi: ufs: Handle LINERESET indication i..
git tree: android-5.4
console output: https://syzkaller.appspot.com/x/log.txt?x=134d0759900000
kernel config: https://syzkaller.appspot.com/x/.config?x=cfb1b86f84d1d53d
dashboard link: https://syzkaller.appspot.com/bug?extid=9811aace89fc431b319b
compiler: Android (6032204 based on r370808) clang version 10.0.1 (https://android.googlesource.com/toolchain/llvm-project 6e765c10313d15c02ab29977a82938f66742c3a9)

Unfortunately, I don't have any reproducer for this issue yet.

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

BUG: unable to handle page fault for address: ffffffffa0138136
#PF: supervisor instruction fetch in kernel mode
#PF: error_code(0x0010) - not-present page
PGD 4c0f067 P4D 4c0f067 PUD 4c10063 PMD 1d4ed0067 PTE 0
Oops: 0010 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 375 Comm: syz-executor.1 Not tainted 5.4.63-syzkaller-00009-g2e92971666a3 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:0xffffffffa0138136
Code: Bad RIP value.
RSP: 0018:ffff8881949b7d18 EFLAGS: 00010246
RAX: 1ffff92000010206 RBX: dffffc0000000000 RCX: ffff8881cffe9f00
RDX: 0000000000000000 RSI: ffffc90000081038 RDI: ffff8881949b7d60
RBP: ffff8881949b7dd0 R08: ffffffff81484e63 R09: fffffbfff09b25a5
R10: fffffbfff09b25a5 R11: 0000000000000000 R12: dffffc0000000000
R13: ffffc90000081000 R14: ffff8881949b7d60 R15: 00000000000000e4
FS: 0000000003134940(0000) GS:ffff8881db800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffffa013810c CR3: 000000019498e001 CR4: 00000000001606f0
DR0: 0000000020000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000600
Call Trace:
trace_sys_enter include/trace/events/syscalls.h:18 [inline]
syscall_trace_enter+0x940/0xa70 arch/x86/entry/common.c:124
do_syscall_64+0x69/0x150 arch/x86/entry/common.c:286
entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x4603fa
Code: 25 18 00 00 00 00 74 01 f0 48 0f b1 3d 6f 9a 24 01 48 39 c2 75 da f3 c3 0f 1f 84 00 00 00 00 00 48 63 ff b8 e4 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 06 f3 c3 0f 1f 40 00 48 c7 c2 d4 ff ff ff f7
RSP: 002b:00007ffe43bcde28 EFLAGS: 00000246 ORIG_RAX: 00000000000000e4
RAX: ffffffffffffffda RBX: 00000000003277e0 RCX: 00000000004603fa
RDX: 0000000000000000 RSI: 00007ffe43bcde30 RDI: 0000000000000001
RBP: 00000000000022b5 R08: 0000000000000001 R09: 0000000003134940
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000001
R13: 00007ffe43bcde90 R14: 0000000000327778 R15: 00007ffe43bcdea0
Modules linked in:
CR2: ffffffffa0138136
---[ end trace 66fea7fd71aeada0 ]---
RIP: 0010:0xffffffffa0138136
Code: Bad RIP value.
RSP: 0018:ffff8881949b7d18 EFLAGS: 00010246
RAX: 1ffff92000010206 RBX: dffffc0000000000 RCX: ffff8881cffe9f00
RDX: 0000000000000000 RSI: ffffc90000081038 RDI: ffff8881949b7d60
RBP: ffff8881949b7dd0 R08: ffffffff81484e63 R09: fffffbfff09b25a5
R10: fffffbfff09b25a5 R11: 0000000000000000 R12: dffffc0000000000
R13: ffffc90000081000 R14: ffff8881949b7d60 R15: 00000000000000e4
FS: 0000000003134940(0000) GS:ffff8881db800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffffa013810c CR3: 000000019498e001 CR4: 00000000001606f0
DR0: 0000000020000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000600


---
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]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.