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=-13.3 required=3.0 tests=BAYES_00,DKIMWL_WL_MED, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_IN_DEF_DKIM_WL autolearn=no 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 718EBC433FE for ; Mon, 6 Sep 2021 17:40:51 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 470286103B for ; Mon, 6 Sep 2021 17:40:51 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S244152AbhIFRlz (ORCPT ); Mon, 6 Sep 2021 13:41:55 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:48152 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S244067AbhIFRly (ORCPT ); Mon, 6 Sep 2021 13:41:54 -0400 Received: from mail-ot1-x32e.google.com (mail-ot1-x32e.google.com [IPv6:2607:f8b0:4864:20::32e]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D6D3BC06175F for ; Mon, 6 Sep 2021 10:40:49 -0700 (PDT) Received: by mail-ot1-x32e.google.com with SMTP id v33-20020a0568300921b0290517cd06302dso9542816ott.13 for ; Mon, 06 Sep 2021 10:40:49 -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=IGzDP1P9SV//47D/1bbDt2xJ8d6dN94V6Uu4MHonLGI=; b=dXQlueRL6yCC1LFm1O4+GsWqrR+kOWkG/f8PNuQDaHoLdUfzrTSsZz3WR3siWSF5oA IRCI/icPdjCL7akV7URsxiE/0yquIkgj0vSN3ktHWvDrEWh0dkUe8l+lnsNLVoXQkiXG kb8R8TmcIH/oW6hTYYmUrIjcJY/o8ZZR30VQygzo9NkceFnkMOl+DLjQHT6lItC77g74 YUJsSW3DxMcfepfANzD9H8W/lRq6KYQJsEp+Z5KtXFX3Uwd39/TGCJfkvmJxdwTGQbO/ I44RFj3of0utGIURwNZsN+NGymZIzTJLoS6P5/VEgSzbRaffutKNTbpLavTB8Q4uj5BC Ngsw== 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=IGzDP1P9SV//47D/1bbDt2xJ8d6dN94V6Uu4MHonLGI=; b=mSh91ZN4j+jGTqrzpdLH7pFryqUV31a2+wBUu0jbWQ/K8rSNCI81HkkLSudpOKW3Pe +33+mpl13BqVY50CcmBjlH1wCDcvhH834zcefCq9/YwQ9vTPRGzzu7jlCV7rou2Py4qQ fpmViZf4qbbdAKa7SggfwpCu9sHknXFgODXikLOMHarv3sOz7AEyNo+EZ2WMhzSRKuFA sjdrd0/alZwhA7ZAaxVpmzgkus5Zqw6oJ2BMHHoVYkpy+UaltKvcEb9DowVWZIa1hjwd +oxb9fIWb6ggcRIe8ztawnIN6gXhh8OQzOAFNZSFhirSnnMLaVUBdpjfcDQvWMp2ZFbW /qeg== X-Gm-Message-State: AOAM531+QblZ8mB0QtsoqIC1ssKuDWmbCGmifOJXqpCP+6a8xlPojZ9K KU1lQZYEeGznu/POvAjRbKHOlqgu6maCrwS2LIdWgg== X-Google-Smtp-Source: ABdhPJxXk8NGnRG2SjvFy0AvMFnXSEzj53HK6kZKZ3zdKO1ioFir7yFoE8Smana1chGOAcxs4SmWH4Zj3COImxKIgkI= X-Received: by 2002:a05:6830:1bf1:: with SMTP id k17mr11577115otb.295.1630950048986; Mon, 06 Sep 2021 10:40:48 -0700 (PDT) MIME-Version: 1.0 References: <000000000000bc92ac05cb4ead3e@google.com> In-Reply-To: From: Marco Elver Date: Mon, 6 Sep 2021 19:40:37 +0200 Message-ID: Subject: Re: [syzbot] linux-next test error: KASAN: null-ptr-deref Read in fuse_conn_put To: Miklos Szeredi Cc: syzbot , linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, Linux-Next Mailing List , Stephen Rothwell , syzkaller-bugs Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-fsdevel@vger.kernel.org On Mon, 6 Sept 2021 at 19:35, Miklos Szeredi wrote: > > On Mon, 6 Sept 2021 at 18:59, Marco Elver wrote: > > > > On Mon, 6 Sept 2021 at 13:56, Miklos Szeredi wrote: > > > Thanks, > > > > > > Force pushed fixed commit 660585b56e63 ("fuse: wait for writepages in > > > syncfs") to fuse.git#for-next. > > > > > > This is fixed as far as I'm concerned, not sure how to tell that to syzbot. > > > > Thanks -- we can let syzbot know: > > > > #syz fix: fuse: wait for writepages in syncfs > > > > (The syntax is just "#syz fix: ".) > > Yeah, but that patch has several versions, one of which is broken. > Syzbot can't tell the difference just based on the title. True, and a general problem with trying to track -next, where even commit hashes might change. For -next, we can probably live with just marking the problem fixed, meaning anyone checking the issue will see a fix exists (and not invest time in trying to fix it). If the problem persists, syzbot will just keep complaining. ;-)