kernel panic: stack is corrupted in __schedule (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: f81e94e91878 Add linux-next specific files for 20211125
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1381cf06b00000
kernel config: https://syzkaller.appspot.com/x/.config?x=be9183de0824e4d7
dashboard link: https://syzkaller.appspot.com/bug?extid=142e97ab5e57fabf6553
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
CC: [linux-...@vger.kernel.org lu...@kernel.org pet...@infradead.org tg...@linutronix.de]

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+142e97...@syzkaller.appspotmail.com

Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: __schedule+0x49fc/0x4d90 kernel/sched/core.c:6301
CPU: 0 PID: 11793 Comm: syz-executor.2 Not tainted 5.16.0-rc2-next-20211125-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106
panic+0x2b0/0x6dd kernel/panic.c:233
__stack_chk_fail+0x15/0x20 kernel/panic.c:687
__schedule+0x49fc/0x4d90 kernel/sched/core.c:6301
preempt_schedule_irq+0x4e/0x90 kernel/sched/core.c:6708
irqentry_exit+0x31/0x80 kernel/entry/common.c:425
asm_sysvec_apic_timer_interrupt+0x12/0x20 arch/x86/include/asm/idtentry.h:638
RIP: 0010:sock_wmalloc+0x0/0x120 net/core/sock.c:2427
Code: e9 a8 fd ff ff 4c 89 e7 e8 bd eb 96 fa e9 96 fe ff ff 4c 89 ef e8 30 ec 96 fa e9 da fe ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 <41> 56 41 55 41 89 cd 41 54 41 89 d4 55 48 89 fd 53 48 89 f3 e8 87
RSP: 0018:ffffc900142ef928 EFLAGS: 00000202
RAX: 0000000000000007 RBX: 0000000000000000 RCX: 0000000000000cc0
RDX: 0000000000000000 RSI: 0000000000000016 RDI: ffff88807aac1000
RBP: ffff88807aac1000 R08: 00000000000005ea R09: 0000000000000001
R10: ffffffff850c6f6e R11: 0000000000000000 R12: ffff88806e88c000
R13: 0000000000000010 R14: 0000000000000010 R15: 0000000000000006
pppoe_sendmsg+0x2b9/0x750 drivers/net/ppp/pppoe.c:867
sock_sendmsg_nosec net/socket.c:704 [inline]
sock_sendmsg+0xcf/0x120 net/socket.c:724
____sys_sendmsg+0x331/0x810 net/socket.c:2409
___sys_sendmsg+0xf3/0x170 net/socket.c:2463
__sys_sendmmsg+0x195/0x470 net/socket.c:2549
__do_sys_sendmmsg net/socket.c:2578 [inline]
__se_sys_sendmmsg net/socket.c:2575 [inline]
__x64_sys_sendmmsg+0x99/0x100 net/socket.c:2575
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:0x7f6618ed6ae9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 bc ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f661642b188 EFLAGS: 00000246 ORIG_RAX: 0000000000000133
RAX: ffffffffffffffda RBX: 00007f6618fea020 RCX: 00007f6618ed6ae9
RDX: 04000000000000eb RSI: 000000002000d180 RDI: 0000000000000006
RBP: 00007f6618f30f6d R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffcf1170e8f R14: 00007f661642b300 R15: 0000000000022000
</TASK>
Kernel Offset: disabled
Rebooting in 86400 seconds..
----------------
Code disassembly (best guess):
0: e9 a8 fd ff ff jmpq 0xfffffdad
5: 4c 89 e7 mov %r12,%rdi
8: e8 bd eb 96 fa callq 0xfa96ebca
d: e9 96 fe ff ff jmpq 0xfffffea8
12: 4c 89 ef mov %r13,%rdi
15: e8 30 ec 96 fa callq 0xfa96ec4a
1a: e9 da fe ff ff jmpq 0xfffffef9
1f: 66 66 2e 0f 1f 84 00 data16 nopw %cs:0x0(%rax,%rax,1)
26: 00 00 00 00
* 2a: 41 56 push %r14 <-- trapping instruction
2c: 41 55 push %r13
2e: 41 89 cd mov %ecx,%r13d
31: 41 54 push %r12
33: 41 89 d4 mov %edx,%r12d
36: 55 push %rbp
37: 48 89 fd mov %rdi,%rbp
3a: 53 push %rbx
3b: 48 89 f3 mov %rsi,%rbx
3e: e8 .byte 0xe8
3f: 87 .byte 0x87


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