BUG: unable to handle kernel paging request in wait_consider_task (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 6b7b0056 Linux 4.19.192
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=16c0c0dbd00000
kernel config: https://syzkaller.appspot.com/x/.config?x=bf82863248bf693f
dashboard link: https://syzkaller.appspot.com/bug?extid=8aca2feef90795f4af28

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+8aca2f...@syzkaller.appspotmail.com

BUG: unable to handle kernel paging request at ffffffffffffff6c
PGD 9e6e067 P4D 9e6e067 PUD 9e70067 PMD 0
Oops: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 8141 Comm: syz-executor.1 Not tainted 4.19.192-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:__read_once_size include/linux/compiler.h:261 [inline]
RIP: 0010:wait_consider_task+0xae/0x3910 kernel/exit.c:1333
Code: 8e 6c 04 00 00 48 89 c8 48 89 4c 24 10 48 c1 e8 03 0f b6 14 28 48 89 c8 83 e0 07 83 c0 03 38 d0 7c 08 84 d2 0f 85 4b 1c 00 00 <45> 8b a6 6c 04 00 00 bf 10 00 00 00 44 89 e6 e8 de 10 2a 00 41 83
RSP: 0018:ffff8880964efb00 EFLAGS: 00010246
RAX: 0000000000000007 RBX: 0000000000000000 RCX: ffffffffffffff6c
RDX: 0000000000000000 RSI: ffffffff81386982 RDI: ffff8880964efd00
RBP: dffffc0000000000 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000000 R12: ffff8880964efd00
R13: ffff8880968160c0 R14: fffffffffffffb00 R15: ffff8880968165b0
FS: 0000000003058400(0000) GS:ffff8880ba100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffffffffff6c CR3: 000000009f5a1000 CR4: 00000000001406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
do_wait_thread kernel/exit.c:1442 [inline]
do_wait+0x429/0x9c0 kernel/exit.c:1513
kernel_wait4+0x14c/0x260 kernel/exit.c:1655
__do_sys_wait4 kernel/exit.c:1667 [inline]
__se_sys_wait4+0x149/0x160 kernel/exit.c:1663
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x464a77
Code: 89 7c 24 10 48 89 4c 24 18 e8 d5 44 02 00 4c 8b 54 24 18 8b 54 24 14 41 89 c0 48 8b 74 24 08 8b 7c 24 10 b8 3d 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 31 44 89 c7 89 44 24 10 e8 05 45 02 00 8b 44
RSP: 002b:00007ffed5b3e650 EFLAGS: 00000293 ORIG_RAX: 000000000000003d
RAX: ffffffffffffffda RBX: 00000000000012b6 RCX: 0000000000464a77
RDX: 0000000040000001 RSI: 00007ffed5b3e6ec RDI: 00000000ffffffff
RBP: 00007ffed5b3e6ec R08: 0000000000000000 R09: 0000009fd74ac266
R10: 0000000000000000 R11: 0000000000000293 R12: 0000000000000001
R13: 0000000000090daf R14: 0000000000000000 R15: 00007ffed5b3e750
Modules linked in:
CR2: ffffffffffffff6c
---[ end trace f41d91a2e6d0eb97 ]---
RIP: 0010:__read_once_size include/linux/compiler.h:261 [inline]
RIP: 0010:wait_consider_task+0xae/0x3910 kernel/exit.c:1333
Code: 8e 6c 04 00 00 48 89 c8 48 89 4c 24 10 48 c1 e8 03 0f b6 14 28 48 89 c8 83 e0 07 83 c0 03 38 d0 7c 08 84 d2 0f 85 4b 1c 00 00 <45> 8b a6 6c 04 00 00 bf 10 00 00 00 44 89 e6 e8 de 10 2a 00 41 83
RSP: 0018:ffff8880964efb00 EFLAGS: 00010246
RAX: 0000000000000007 RBX: 0000000000000000 RCX: ffffffffffffff6c
RDX: 0000000000000000 RSI: ffffffff81386982 RDI: ffff8880964efd00
RBP: dffffc0000000000 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000000 R12: ffff8880964efd00
R13: ffff8880968160c0 R14: fffffffffffffb00 R15: ffff8880968165b0
FS: 0000000003058400(0000) GS:ffff8880ba100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffffffffff6c CR3: 000000009f5a1000 CR4: 00000000001406e0
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]

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