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

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: ff1176468d36 Linux 5.14-rc3
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1708e862300000
kernel config: https://syzkaller.appspot.com/x/.config?x=40eef000d7648480
dashboard link: https://syzkaller.appspot.com/bug?extid=338d77cdbb8fca71ffe1
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.1
CC: [ak...@linux-foundation.org chri...@brauner.io ebie...@xmission.com jnew...@torproject.org linux-...@vger.kernel.org min...@kernel.org ol...@redhat.com pet...@infradead.org]

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+338d77...@syzkaller.appspotmail.com

BUG: unable to handle page fault for address: ffffffffffffff64
#PF: supervisor read access in kernel mode
#PF: error_code(0x0000) - not-present page
PGD b68f067 P4D b68f067 PUD b691067 PMD 0
Oops: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 8462 Comm: syz-executor.2 Not tainted 5.14.0-rc3-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:wait_consider_task+0xae/0x3b80 kernel/exit.c:1288
Code: 8f ec 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 c2 1a 00 00 <45> 8b a7 ec 04 00 00 bf 10 00 00 00 44 89 e6 e8 7e 29 30 00 41 83
RSP: 0018:ffffc90001d2fb60 EFLAGS: 00010246
RAX: 0000000000000007 RBX: 0000000000000000 RCX: ffffffffffffff64
RDX: 0000000000000000 RSI: ffffffff81456872 RDI: ffffc90001d2fd18
RBP: dffffc0000000000 R08: 0000000000000000 R09: ffffffff8b60a083
R10: ffffffff8145aa46 R11: 0000000000000000 R12: dffffc0000000000
R13: ffff888032b0b880 R14: 0000000000000000 R15: fffffffffffffa78
FS: 0000000002ff1400(0000) GS:ffff8880b9d00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffffffffff64 CR3: 0000000072615000 CR4: 0000000000350ee0
Call Trace:
do_wait_thread kernel/exit.c:1397 [inline]
do_wait+0x6ca/0xce0 kernel/exit.c:1514
kernel_wait4+0x14c/0x260 kernel/exit.c:1677
__do_sys_wait4+0x13f/0x150 kernel/exit.c:1705
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x44/0xae
RIP: 0033:0x464a87
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:00007ffd0f1b8100 EFLAGS: 00000293 ORIG_RAX: 000000000000003d
RAX: ffffffffffffffda RBX: 0000000000000cd6 RCX: 0000000000464a87
RDX: 0000000040000001 RSI: 00007ffd0f1b819c RDI: 00000000ffffffff
RBP: 00007ffd0f1b819c R08: 0000000000000000 R09: 00007ffd0f1e4080
R10: 0000000000000000 R11: 0000000000000293 R12: 0000000000000032
R13: 00000000000b16fc R14: 0000000000000001 R15: 00007ffd0f1b8200
Modules linked in:
CR2: ffffffffffffff64
---[ end trace 3f9ae5191ef5e3e3 ]---
RIP: 0010:wait_consider_task+0xae/0x3b80 kernel/exit.c:1288
Code: 8f ec 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 c2 1a 00 00 <45> 8b a7 ec 04 00 00 bf 10 00 00 00 44 89 e6 e8 7e 29 30 00 41 83
RSP: 0018:ffffc90001d2fb60 EFLAGS: 00010246
RAX: 0000000000000007 RBX: 0000000000000000 RCX: ffffffffffffff64
RDX: 0000000000000000 RSI: ffffffff81456872 RDI: ffffc90001d2fd18
RBP: dffffc0000000000 R08: 0000000000000000 R09: ffffffff8b60a083
R10: ffffffff8145aa46 R11: 0000000000000000 R12: dffffc0000000000
R13: ffff888032b0b880 R14: 0000000000000000 R15: fffffffffffffa78
FS: 0000000002ff1400(0000) GS:ffff8880b9d00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffffffffff64 CR3: 0000000072615000 CR4: 0000000000350ee0


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