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 X-Spam-Level: X-Spam-Status: No, score=-18.2 required=3.0 tests=BAYES_00,DKIMWL_WL_MED, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED, USER_IN_DEF_DKIM_WL autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 336DDC43460 for ; Fri, 16 Apr 2021 07:21:28 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id ED381610E7 for ; Fri, 16 Apr 2021 07:21:27 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S239131AbhDPHVu (ORCPT ); Fri, 16 Apr 2021 03:21:50 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:32784 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230466AbhDPHVt (ORCPT ); Fri, 16 Apr 2021 03:21:49 -0400 Received: from mail-qv1-xf2d.google.com (mail-qv1-xf2d.google.com [IPv6:2607:f8b0:4864:20::f2d]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 471B5C061574 for ; Fri, 16 Apr 2021 00:21:25 -0700 (PDT) Received: by mail-qv1-xf2d.google.com with SMTP id j3so12989232qvs.1 for ; Fri, 16 Apr 2021 00:21:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=wjmD73GPpy2QbsTxbpbJAucxJYCt7dBmfHIx/C3Hj5U=; b=nu9OwTXrpMDNPvqq2iAKRq4pBy+2naRJYAi61Oux7KKTpTV2uDlMOELJRZe/KW0Z/l Z+6XaCmV9b2o9Jc3tpiK+RPxHLVZMYnun6G1e84agmCOQYYhmaNqZI6pX4+WR5MC3sCV 7/OEra7nrNmsZGborSeXxxr+uGqVI3QrQFpRmoHfhwvD/Xxi7ZsxP2TnIudtTvWCB7Q5 axzqI1g1A7zuQgAhk3ENd88sCzhnWukzNCc7ROW9RTQwJ3H4mcmCsNBDicoBaDvwAyNy wXiszwJWU9UvkztZu7mB8gu7CVYnQWOOr7p5cdgvgYmZ7ERtxtr6tXD7BJDyg6Amo9/E nifQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=wjmD73GPpy2QbsTxbpbJAucxJYCt7dBmfHIx/C3Hj5U=; b=drHU/520ipbescIngMSVJyvjeEnQefIMHM1jRYTdlKhosN3YDFvM7x8XjEA5qzDz2T OiBy39PCE+Me16hxg1ytOdwHQyELUPUUpzg9r8XAFpfoHxhup4DPbPzIMwd5ZaOlXs2Y KFcQz1Njh8qB2tGrOhAmwqSiJhzWarxRD3XJnAx6wPBoaet/NIQ/hy3ho4Wz8qDLvb9u 17qbL5QCtU9oRnWSCQXd2a3nONvrMwBpnIY+DXGr6beFLbwyoIkQotxgwOeMGqTbngmf VLz9v379qCa/+7fzdzHQnM0R9vOY+yQ5RttdM1Fose34C8YlS+WqOmFdJVT7zj/97kkJ vqsw== X-Gm-Message-State: AOAM532t4WpsLzxd1sRH8pvob8HAzAU8buVcMCGcnj07FYiKdgSjSWXb xjszAfxnMoGkNhqPjn6OFH0418uSByQHjGhOI6ecVA== X-Google-Smtp-Source: ABdhPJw3kEHh/UQ6eNJ/oZf4yxIHMjsXukXccmBLxb3LC8DY+slR11/4BD4jxSF26gGaypErVDi6pHqHlV2Y+52cwo4= X-Received: by 2002:a0c:d786:: with SMTP id z6mr6484078qvi.18.1618557684261; Fri, 16 Apr 2021 00:21:24 -0700 (PDT) MIME-Version: 1.0 References: <00000000000075c58405bfd6228c@google.com> <20210413161311.GC1454681@rowland.harvard.edu> <20210413165724.GD1454681@rowland.harvard.edu> <20210415205957.GA19917@rowland.harvard.edu> In-Reply-To: <20210415205957.GA19917@rowland.harvard.edu> From: Dmitry Vyukov Date: Fri, 16 Apr 2021 09:21:12 +0200 Message-ID: Subject: Re: [syzbot] general protection fault in gadget_setup To: Alan Stern Cc: syzbot , Andrey Konovalov , Felipe Balbi , Dan Carpenter , Greg Kroah-Hartman , LKML , USB list , syzkaller-bugs , syzkaller Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Apr 15, 2021 at 10:59 PM Alan Stern wrote: > > On Tue, Apr 13, 2021 at 07:11:11PM +0200, Dmitry Vyukov wrote: > > On Tue, Apr 13, 2021 at 6:57 PM Alan Stern wrote: > > > > > > On Tue, Apr 13, 2021 at 06:47:47PM +0200, Dmitry Vyukov wrote: > > > > On Tue, Apr 13, 2021 at 6:13 PM Alan Stern wrote: > > > > > Hopefully this patch will make the race a lot more likely to occur. Is > > > > > there any way to tell syzkaller to test it, despite the fact that > > > > > syzkaller doesn't think it has a reproducer for this issue? > > > > > > > > If there is no reproducer the only way syzbot can test it is if it's > > > > in linux-next under CONFIG_DEBUG_AID_FOR_SYZBOT: > > > > http://bit.do/syzbot#no-custom-patches > > > > > > There _is_ a theoretical reproducer: the test that provoked syzkaller's > > > original bug report. But syzkaller doesn't realize that it is (or may > > > be) a reproducer. > > > > > > It ought to be possible to ask syzkaller to run a particular test that > > > it has done before, with a patch applied -- and without having to add > > > anything to linux-next. > > > > Yes, this is possible: > > http://bit.do/syzbot#syzkaller-reproducers > > That's not really what I had in mind. I don't want to spend the time > and effort installing syskaller on my own system; I want to tell syzbot > to run a particular syzkaller program (the one that originally led to > this bug report) on a patched kernel. > > The syzbot instructions say that it can test bugs with reproducers. The > problem here is that there doesn't seem to be any way to tell it to use > a particular syzkaller program as a reproducer. Hi Alan, This makes sense and I've found an existing feature request: https://github.com/google/syzkaller/issues/1611 I've added a reference to this thread there.