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

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 414e6c8e941c ANDROID: fix up abi issue with struct snd_pcm..
git tree: android12-5.10-lts
console output: https://syzkaller.appspot.com/x/log.txt?x=158fb060f00000
kernel config: https://syzkaller.appspot.com/x/.config?x=19b81eb0d2d939d9
dashboard link: https://syzkaller.appspot.com/bug?extid=67a4553d622787cb9f53
compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=144ed960f00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1434dc88f00000

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

BUG: stack guard page was hit at ffffc90003187f98 (stack is ffffc90003188000..ffffc9000318ffff)
kernel stack overflow (double-fault): 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 796 Comm: syz-executor304 Not tainted 5.10.109-syzkaller-00693-g414e6c8e941c #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:__update_load_avg_se+0x40/0xb90 kernel/sched/pelt.c:372
Code: f7 49 89 fe 48 be 00 00 00 00 00 fc ff df 48 8d 7a 38 48 89 f8 48 c1 e8 03 8a 04 30 84 c0 0f 85 38 08 00 00 8b 43 38 45 31 ed <89> 45 a8 85 c0 41 0f 95 c4 48 89 5d b0 48 81 c3 58 01 00 00 48 89
RSP: 0018:ffffc90003187fa0 EFLAGS: 00010046
RAX: 0000000000000000 RBX: ffff88810c856340 RCX: dffffc0000000000
RDX: ffff88810c856340 RSI: dffffc0000000000 RDI: ffff88810c856378
RBP: ffffc90003188030 R08: 00000000000001c3 R09: fffffbfff0c5ebeb
R10: fffffbfff0c5ebeb R11: 1ffffffff0c5ebea R12: dffffc0000000000
R13: 0000000000000000 R14: 0000001122634f2b R15: ffff8881f7156000
FS: 0000555555cee3c0(0000) GS:ffff8881f7100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffc90003187f98 CR3: 000000010eae9000 CR4: 00000000003506a0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
Modules linked in:
---[ end trace 7f3e83c1acb3b509 ]---
RIP: 0010:__update_load_avg_se+0x40/0xb90 kernel/sched/pelt.c:372
Code: f7 49 89 fe 48 be 00 00 00 00 00 fc ff df 48 8d 7a 38 48 89 f8 48 c1 e8 03 8a 04 30 84 c0 0f 85 38 08 00 00 8b 43 38 45 31 ed <89> 45 a8 85 c0 41 0f 95 c4 48 89 5d b0 48 81 c3 58 01 00 00 48 89
RSP: 0018:ffffc90003187fa0 EFLAGS: 00010046
RAX: 0000000000000000 RBX: ffff88810c856340 RCX: dffffc0000000000
RDX: ffff88810c856340 RSI: dffffc0000000000 RDI: ffff88810c856378
RBP: ffffc90003188030 R08: 00000000000001c3 R09: fffffbfff0c5ebeb
R10: fffffbfff0c5ebeb R11: 1ffffffff0c5ebea R12: dffffc0000000000
R13: 0000000000000000 R14: 0000001122634f2b R15: ffff8881f7156000
FS: 0000555555cee3c0(0000) GS:ffff8881f7100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffc90003187f98 CR3: 000000010eae9000 CR4: 00000000003506a0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess), 1 bytes skipped:
0: 49 89 fe mov %rdi,%r14
3: 48 be 00 00 00 00 00 movabs $0xdffffc0000000000,%rsi
a: fc ff df
d: 48 8d 7a 38 lea 0x38(%rdx),%rdi
11: 48 89 f8 mov %rdi,%rax
14: 48 c1 e8 03 shr $0x3,%rax
18: 8a 04 30 mov (%rax,%rsi,1),%al
1b: 84 c0 test %al,%al
1d: 0f 85 38 08 00 00 jne 0x85b
23: 8b 43 38 mov 0x38(%rbx),%eax
26: 45 31 ed xor %r13d,%r13d
* 29: 89 45 a8 mov %eax,-0x58(%rbp) <-- trapping instruction
2c: 85 c0 test %eax,%eax
2e: 41 0f 95 c4 setne %r12b
32: 48 89 5d b0 mov %rbx,-0x50(%rbp)
36: 48 81 c3 58 01 00 00 add $0x158,%rbx
3d: 48 rex.W
3e: 89 .byte 0x89


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