[syzbot] usb-testing boot error: kernel panic: corrupted stack end in call_usermodehelper_exec_async

syzbot
2022-08-22T19:48:44Z

Hello,

syzbot found the following issue on:

HEAD commit: ad57410d231d usb: gadget: rndis: use %u instead of %d to p..
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-testing
console output: https://syzkaller.appspot.com/x/log.txt?x=1294c603080000
kernel config: https://syzkaller.appspot.com/x/.config?x=3cb39b084894e9a5
dashboard link: https://syzkaller.appspot.com/bug?extid=0d36a7d5e61d057c150d
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2

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

Kernel panic - not syncing: corrupted stack end detected inside scheduler
CPU: 0 PID: 243 Comm: kworker/u4:1 Not tainted 6.0.0-rc1-syzkaller-00005-gad57410d231d #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/22/2022
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106
panic+0x2c8/0x627 kernel/panic.c:274
schedule_debug kernel/sched/core.c:5737 [inline]
__schedule+0x26dd/0x26f0 kernel/sched/core.c:6388
do_task_dead+0xd1/0x100 kernel/sched/core.c:6512
do_exit+0x18bd/0x2930 kernel/exit.c:847
call_usermodehelper_exec_async+0x418/0x580 kernel/umh.c:125
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
</TASK>
Kernel Offset: disabled
Rebooting in 86400 seconds..

---
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 syzkaller@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.