BUG: stack guard page was hit in corrupted (9)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: d221da1d6fcb Merge d04937ae9490 ("x86/speculation: Warn ab..
git tree: android12-5.10-lts
console output: https://syzkaller.appspot.com/x/log.txt?x=13baf883700000
kernel config: https://syzkaller.appspot.com/x/.config?x=74a3a3b391ca1e24
dashboard link: https://syzkaller.appspot.com/bug?extid=c049c907576aa79e5673
compiler: Debian clang version 11.0.1-2, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=115b36a9700000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=141c4419700000

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

BUG: stack guard page was hit at ffffc90000b6ffd8 (stack is ffffc90000b70000..ffffc90000b77fff)
kernel stack overflow (double-fault): 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 365 Comm: syz-executor191 Not tainted 5.10.104-syzkaller-00370-gd221da1d6fcb #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:stack_trace_save+0x1a/0x1e0 kernel/stacktrace.c:113
Code: 41 5e 41 5f 5d c3 0f 0b 45 31 ed eb e7 0f 1f 00 55 48 89 e5 41 57 41 56 41 55 41 54 53 48 83 e4 e0 48 81 ec a0 00 00 00 89 d3 <89> 74 24 1c 49 89 fc 65 48 8b 04 25 28 00 00 00 48 89 84 24 80 00
RSP: 0018:ffffc90000b6ffe0 EFLAGS: 00010282
RAX: ffffc90000b700c0 RBX: 0000000000000000 RCX: 0000000000000000
RDX: 0000000000000000 RSI: 0000000000000040 RDI: ffffc90000b700c0
RBP: ffffc90000b700b0 R08: dffffc0000000000 R09: ffffc90000b700c0
R10: 0000000000000000 R11: 0000000000000000 R12: ffff88811a133d90
R13: 0000000000000cc0 R14: 0000000000000cc0 R15: ffffc90000b700c0
FS: 000055555719e3c0(0000) GS:ffff8881f7100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffc90000b6ffd8 CR3: 000000011c575000 CR4: 00000000003506a0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
Modules linked in:
---[ end trace 7b875c6d7304e3a7 ]---
RIP: 0010:stack_trace_save+0x1a/0x1e0 kernel/stacktrace.c:113
Code: 41 5e 41 5f 5d c3 0f 0b 45 31 ed eb e7 0f 1f 00 55 48 89 e5 41 57 41 56 41 55 41 54 53 48 83 e4 e0 48 81 ec a0 00 00 00 89 d3 <89> 74 24 1c 49 89 fc 65 48 8b 04 25 28 00 00 00 48 89 84 24 80 00
RSP: 0018:ffffc90000b6ffe0 EFLAGS: 00010282
RAX: ffffc90000b700c0 RBX: 0000000000000000 RCX: 0000000000000000
RDX: 0000000000000000 RSI: 0000000000000040 RDI: ffffc90000b700c0
RBP: ffffc90000b700b0 R08: dffffc0000000000 R09: ffffc90000b700c0
R10: 0000000000000000 R11: 0000000000000000 R12: ffff88811a133d90
R13: 0000000000000cc0 R14: 0000000000000cc0 R15: ffffc90000b700c0
FS: 000055555719e3c0(0000) GS:ffff8881f7100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffc90000b6ffd8 CR3: 000000011c575000 CR4: 00000000003506a0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
0: 41 5e pop %r14
2: 41 5f pop %r15
4: 5d pop %rbp
5: c3 retq
6: 0f 0b ud2
8: 45 31 ed xor %r13d,%r13d
b: eb e7 jmp 0xfffffff4
d: 0f 1f 00 nopl (%rax)
10: 55 push %rbp
11: 48 89 e5 mov %rsp,%rbp
14: 41 57 push %r15
16: 41 56 push %r14
18: 41 55 push %r13
1a: 41 54 push %r12
1c: 53 push %rbx
1d: 48 83 e4 e0 and $0xffffffffffffffe0,%rsp
21: 48 81 ec a0 00 00 00 sub $0xa0,%rsp
28: 89 d3 mov %edx,%ebx
* 2a: 89 74 24 1c mov %esi,0x1c(%rsp) <-- trapping instruction
2e: 49 89 fc mov %rdi,%r12
31: 65 48 8b 04 25 28 00 mov %gs:0x28,%rax
38: 00 00
3a: 48 rex.W
3b: 89 .byte 0x89
3c: 84 24 80 test %ah,(%rax,%rax,4)


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

[Tadeusz Struk]

#syz dup: BUG: stack guard page was hit in file_open