general protection fault in account_kernel_stack (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: b765a32a Merge tag 'scsi-fixes' of git://git.kernel.org/pu..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=17069ae9900000
kernel config: https://syzkaller.appspot.com/x/.config?x=3c5f6ce8d5b68299
dashboard link: https://syzkaller.appspot.com/bug?extid=1ff00be9dd24594ed8e1
compiler: gcc (GCC) 10.1.0-syz 20200507
CC: [ak...@linux-foundation.org chri...@brauner.io kees...@chromium.org linux-...@vger.kernel.org lu...@amacapital.net mi...@kernel.org pet...@infradead.org shak...@google.com w...@chromium.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+1ff00b...@syzkaller.appspotmail.com

general protection fault, probably for non-canonical address 0xe000ea000000ee00: 0000 [#1] PREEMPT SMP KASAN
KASAN: maybe wild-memory-access in range [0x0007700000077000-0x0007700000077007]
CPU: 1 PID: 0 Comm: swapper/1 Not tainted 5.9.0-rc3-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:account_kernel_stack+0xae/0x5b0 kernel/fork.c:384
Code: fc ff df 48 89 fa 48 c1 ea 03 80 3c 02 00 0f 85 7f 04 00 00 48 b8 00 00 00 00 00 fc ff df 49 8b 5c 24 20 48 89 da 48 c1 ea 03 <80> 3c 02 00 0f 85 52 04 00 00 4d 85 ed 4c 8b 3b 0f 84 c2 03 00 00
RSP: 0018:ffffc90000d3fcb0 EFLAGS: 00010206
RAX: dffffc0000000000 RBX: 0007700000077000 RCX: ffffffff8144a50c
RDX: 0000ee000000ee00 RSI: ffffffff81448268 RDI: ffff88800011fba0
RBP: 00000000ffffffe0 R08: 0000000000000001 R09: ffff888066b7f643
R10: 0000000000000080 R11: 0000000000000000 R12: ffff88800011fb80
R13: ffffffff812a8910 R14: 0000000000000000 R15: ffff888066b7f638
FS: 0000000000000000(0000) GS:ffff8880ae700000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ff6f8a88db8 CR3: 0000000098fde000 CR4: 00000000001526e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
release_task_stack kernel/fork.c:425 [inline]
put_task_stack+0xdf/0x480 kernel/fork.c:437
finish_task_switch+0x52a/0x750 kernel/sched/core.c:3649
context_switch kernel/sched/core.c:3781 [inline]
__schedule+0xeb1/0x2230 kernel/sched/core.c:4527
schedule_idle+0x53/0x90 kernel/sched/core.c:4630
do_idle+0x3a3/0x730 kernel/sched/idle.c:301
cpu_startup_entry+0x14/0x20 kernel/sched/idle.c:369
secondary_startup_64+0xa4/0xb0 arch/x86/kernel/head_64.S:243
Modules linked in:
---[ end trace e075683eefa43914 ]---
RIP: 0010:account_kernel_stack+0xae/0x5b0 kernel/fork.c:384
Code: fc ff df 48 89 fa 48 c1 ea 03 80 3c 02 00 0f 85 7f 04 00 00 48 b8 00 00 00 00 00 fc ff df 49 8b 5c 24 20 48 89 da 48 c1 ea 03 <80> 3c 02 00 0f 85 52 04 00 00 4d 85 ed 4c 8b 3b 0f 84 c2 03 00 00
RSP: 0018:ffffc90000d3fcb0 EFLAGS: 00010206
RAX: dffffc0000000000 RBX: 0007700000077000 RCX: ffffffff8144a50c
RDX: 0000ee000000ee00 RSI: ffffffff81448268 RDI: ffff88800011fba0
RBP: 00000000ffffffe0 R08: 0000000000000001 R09: ffff888066b7f643
R10: 0000000000000080 R11: 0000000000000000 R12: ffff88800011fb80
R13: ffffffff812a8910 R14: 0000000000000000 R15: ffff888066b7f638
FS: 0000000000000000(0000) GS:ffff8880ae700000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ff6f8a88db8 CR3: 0000000098fde000 CR4: 00000000001526e0
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.