From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id E9144C28D13 for ; Mon, 22 Aug 2022 19:48:44 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S237625AbiHVTsl (ORCPT ); Mon, 22 Aug 2022 15:48:41 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35798 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S237169AbiHVTsd (ORCPT ); Mon, 22 Aug 2022 15:48:33 -0400 Received: from mail-il1-f199.google.com (mail-il1-f199.google.com [209.85.166.199]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4877213F02 for ; Mon, 22 Aug 2022 12:48:32 -0700 (PDT) Received: by mail-il1-f199.google.com with SMTP id q10-20020a056e020c2a00b002dedb497c7fso9062487ilg.16 for ; Mon, 22 Aug 2022 12:48:32 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:from:subject:message-id:date:mime-version:x-gm-message-state :from:to:cc; bh=pz50IIbxyx33+nWabTiAdIsjgxs4XJ7Q5EWkKJhISNg=; b=NzKD7HzR8vMPR32QL8uYxWZVaTYhA5pm7Q2JOcP6KB9ljsqL/oA7fAB3tLSauqkOlQ I98TozjJEybZRy1J4WAmQQEC0i1zTmcRJjgyaT8qs5T50/91NsSwH2lohfXDDxKOt7pS qCl5FfFX8yeL2cWH3+TXv3Nv+JqPKlJAx4QtNOjT6JnfQbQTXwbMcRAcxo1oT5C+nGph PEHcZhDu7UacOfw3YW0dSA0ZADOboIzXDH0rB3XE/6Z4SHTzTt7WFV7u0IuKdrtGzSNF 0EfT6ZxV2Bo1WdCC0QJvCH1rvkWOHt1yk3bxopAkrxTv7iNTgJGm88sL/4O/d7L0onAf NnYw== X-Gm-Message-State: ACgBeo0ut/Hd3WkRdsX5gDcHYAUsK44xbZGya+eTXf/w4CAS449oAdGC DutfC0XPQOagCp5IOjw6Wh3GTSrkSTQ11MeeUr/j1/WilYqv X-Google-Smtp-Source: AA6agR7IyVH/TvQuqqZYaHxZxwdgjhsI1d+Eyhjg2/4/W5pTNpbeW/z7IswKz3Y+9DivWSpJOH43xvPM2ML1YbcajltVJReWzHjQ MIME-Version: 1.0 X-Received: by 2002:a05:6638:31c1:b0:33f:2450:46a9 with SMTP id n1-20020a05663831c100b0033f245046a9mr10085585jav.45.1661197711680; Mon, 22 Aug 2022 12:48:31 -0700 (PDT) Date: Mon, 22 Aug 2022 12:48:31 -0700 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <00000000000081a9cc05e6d9bb84@google.com> Subject: [syzbot] usb-testing boot error: kernel panic: corrupted stack end in call_usermodehelper_exec_async From: syzbot To: brauner@kernel.org, ebiederm@xmission.com, keescook@chromium.org, linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org, syzkaller-bugs@googlegroups.com Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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: __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 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.