From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on gnuweeb.org X-Spam-Level: X-Spam-Status: No, score=-7.6 required=5.0 tests=DKIMWL_WL_MED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_PASS,SPF_SOFTFAIL,URIBL_BLOCKED, USER_IN_DEF_DKIM_WL autolearn=ham autolearn_force=no version=3.4.6 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 82294C433F5 for ; Fri, 20 May 2022 08:42:03 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230143AbiETImB (ORCPT ); Fri, 20 May 2022 04:42:01 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:34674 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1347395AbiETIlc (ORCPT ); Fri, 20 May 2022 04:41:32 -0400 Received: from mail-lf1-x12d.google.com (mail-lf1-x12d.google.com [IPv6:2a00:1450:4864:20::12d]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 52B3766224 for ; Fri, 20 May 2022 01:41:30 -0700 (PDT) Received: by mail-lf1-x12d.google.com with SMTP id bq30so13167619lfb.3 for ; Fri, 20 May 2022 01:41:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=mOM3/bXCDSJ92n64FbMH5hkxby+aWy4nmII/rMMLa6s=; b=aBTsMjpo5a0JI53DGkowLuB+EgUd542Asyjlt9vBPtUGTaLS6s199Hqs9zX1zVmDHf ni9SWEsIYw4KfL41gYhFHrDDvkijSNH0TfSUH+Avfx0HKUak1vMNkrVlUlC9T26x9W7/ ksEArMkLaCAo6g84mSV1nvezZXN6WnfK1/4VhPNX0F7M/SNGDo+3UOQNObkjPMjfg0X1 BZBwiF5AMoD/Uq8ET5Ytcu/1oeIAwdDbZVMgwW9kyh9Y4sumDOA09NsgKsSJRPnK/+zA JpzVAsAEdJJjA+tWHv+2WK/4rkYoacjsa6C8OR1Ru2DEaSbroriOhbXVEx1Rmb5WXA4q fSVw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=mOM3/bXCDSJ92n64FbMH5hkxby+aWy4nmII/rMMLa6s=; b=X5M5yejJyfbgqMWft2+LR4JPTZzdhtf4F4FqPJdQ9FRiBOR3mTMDd/B1m1pYGT//xF ZqTwpNEQONxhOVm4HnEqiEuMzfiZf2kPobxgmk2Z38A4qI4Vba7F7hA19e5jc1ji69Uf fi+P8dbwgodUitxAU0ty6AJu12558KogfFPaKErTiwox3yd5w/FpJX9LNe/bxA843WYx +bZUzNIvTNjCpB6sW1bwQI+Q90PfGbNiGNTmbjdUlKgL1rJqGmeA7AGvbI6blrHqvaWT lvOxqjukHSs9pwp2Vho49DDUy1zE/sqQipxG0UzZCnuMRS4Hoxu7dhU+olqddFIGa2nD TvLw== X-Gm-Message-State: AOAM53138xxr67pnOu/GOy7Kn/S63xmw+nB43evKguGCT+7qwBC0mBZJ id1tsneiTG4iua5iIT8L1l4OO93jAfrGnv/wodOpzA== X-Google-Smtp-Source: ABdhPJwESBHW/XZ/646NXd8royKCOv0R5aOPj1t/RZqKCDp/1YjSS8L0pS0nqqPng00EAJzWLMS4/pUqepkrCBNINew= X-Received: by 2002:a05:6512:696:b0:473:a6ef:175d with SMTP id t22-20020a056512069600b00473a6ef175dmr6305530lfe.540.1653036088376; Fri, 20 May 2022 01:41:28 -0700 (PDT) MIME-Version: 1.0 References: <000000000000f0da6305cb1feacb@google.com> <15a67989-9ad7-11ef-9472-8e16ca6ec11a@kernel.dk> In-Reply-To: <15a67989-9ad7-11ef-9472-8e16ca6ec11a@kernel.dk> From: Dmitry Vyukov Date: Fri, 20 May 2022 10:41:16 +0200 Message-ID: Subject: Re: [syzbot] general protection fault in __io_arm_poll_handler To: Jens Axboe Cc: syzbot , asml.silence@gmail.com, io-uring@vger.kernel.org, linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com, syzkaller Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: io-uring@vger.kernel.org On Sat, 4 Sept 2021 at 02:49, Jens Axboe wrote: > > On 9/3/21 5:47 PM, syzbot wrote: > > Hello, > > > > syzbot has tested the proposed patch and the reproducer did not trigger any issue: > > > > Reported-and-tested-by: syzbot+ba74b85fa15fd7a96437@syzkaller.appspotmail.com > > > > Tested on: > > > > commit: 31efe48e io_uring: fix possible poll event lost in mul.. > > git tree: git://git.kernel.dk/linux-block for-5.15/io_uring > > kernel config: https://syzkaller.appspot.com/x/.config?x=914bb805fa8e8da9 > > dashboard link: https://syzkaller.appspot.com/bug?extid=ba74b85fa15fd7a96437 > > compiler: Debian clang version 11.0.1-2, GNU ld (GNU Binutils for Debian) 2.35.1 > > > > Note: testing is done by a robot and is best-effort only. > > Dmitry, I wonder if there's a way to have syzbot know about what it's > testing and be able to run the pending patches for that tree? I think > we're up to 4 reports now that are all just fallout from the same bug, > and where a patch has been queued up for a few days. Since they all look > different, I can't fault syzbot for thinking they are different, even if > they have the same root cause. > > Any way we can make this situation better? I can't keep replying that we > should test the current branch, and it'd be a shame to have a ton of > dupes. Hi Jens, This somehow fell through the cracks, but better late than never. We could set up a syzbot instance for the io-uring tree. It won't solve the problem directly, but if the branch contains both new development ("for-next") and fixes, it will have good chances of discovering issues before they reach mainline and spread to other trees. Do you think it's a good idea? Is there a branch that contains new development and fixes?