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=-8.3 required=3.0 tests=DKIMWL_WL_MED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,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 2CA61C432C3 for ; Tue, 26 Nov 2019 01:47:14 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id EC3CE20684 for ; Tue, 26 Nov 2019 01:47:13 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=google.com header.i=@google.com header.b="fKk7iNXT" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727209AbfKZBrN (ORCPT ); Mon, 25 Nov 2019 20:47:13 -0500 Received: from mail-pg1-f196.google.com ([209.85.215.196]:36585 "EHLO mail-pg1-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726866AbfKZBrM (ORCPT ); Mon, 25 Nov 2019 20:47:12 -0500 Received: by mail-pg1-f196.google.com with SMTP id k13so8155519pgh.3 for ; Mon, 25 Nov 2019 17:47:12 -0800 (PST) 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=KkZGv+kaMOga5WARXycE1ZR6cg0tzVfNuWa+lDuB6eA=; b=fKk7iNXTahDaTuu4siVHdmD0NjesZJugTBAO521e4DBMSdzUiFWFwplVD/tNz5lnEv GINdVulbR0rZ6ElEFBaDghKkQH7Lbv5boGbJgpixv8LeZpvERzo2qPu+zGbjT/al82sA z62npVcm4VPxwCEnQq5dQQf/a0QQVEWE24gDUEv6KZ1qlqE9UU2QMEtR6fJxaBoKR6V6 gtZmnhU1MDcN0Eys4c26fpYm9Up0lB/o0EBSMt35dyw7SGwIYhyD7fnhIKJBq+GDJkAw bdH7IGoeYKHr6/53EWQAxTK2w2/qNssD7+kxV45f6MRZaXrzK0dwSBgbvNyw+oz04uKS JPMA== 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=KkZGv+kaMOga5WARXycE1ZR6cg0tzVfNuWa+lDuB6eA=; b=N0mWC7QxXwuOzQ74d0H9oczoS8zKwD+ocufMmwKs/YyaLbh4P9gRC5Eo9g+bvcmRPj R34ebTZvyHQ0ArqI1jmQg4el+bxSKgAyQs1LhpgE9dd2PnMes04wBprDFUmjETGCKlXZ A+hT5olA8MGIDV/y1CKa/xEbQRdIWJ/x4v0itq8sd2BoJT62KeyCbxHE5LL6yFRkij9r yBdUMjbI+SJTPgDaPkI3D/QsX3TvLbYd2wMKvfe5bMPT65i8S+mH3cIKrW1LykRjZzP8 8grLGNMqPhAaAzEDrKoKeRmSjNGfBAp/UPFH67UQkWP9plfpQK3jP+lLDOb/fR6cOrXR 3hSQ== X-Gm-Message-State: APjAAAWWjX9Qs1H0YdVl3F8my7E/B1JJU2xMtp2dm4YN1onHqspxQHjc MIT8vtzAWa4ruj+Vw+u72hSXrL6DaGTZtTUkJucoNg== X-Google-Smtp-Source: APXvYqyImvfmdTfyDaHgXSiWPllgqHWf9GpTbhRsh7dw9gJgDmp9BsGWWi66XgRFRpDBOL50K/fZYgB/fkgfjD3GP8s= X-Received: by 2002:a63:4c14:: with SMTP id z20mr27206083pga.10.1574732831450; Mon, 25 Nov 2019 17:47:11 -0800 (PST) MIME-Version: 1.0 References: <201911220351.HPI9gxNo%lkp@intel.com> <20191125185931.GA30548@dennisz-mbp.dhcp.thefacebook.com> <20191126014209.GB21240@intel.com> In-Reply-To: <20191126014209.GB21240@intel.com> From: Nick Desaulniers Date: Mon, 25 Nov 2019 17:47:00 -0800 Message-ID: Subject: Re: [PATCH 05/22] btrfs: add the beginning of async discard, discard workqueue To: Philip Li Cc: Dennis Zhou , Chen Rong , kbuild@lists.01.org, clang-built-linux , kbuild test robot , kbuild-all@lists.01.org, David Sterba , Chris Mason , Josef Bacik , Omar Sandoval , kernel-team@fb.com, linux-btrfs@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Sender: linux-btrfs-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-btrfs@vger.kernel.org On Mon, Nov 25, 2019 at 5:35 PM Philip Li wrote: > > On Mon, Nov 25, 2019 at 11:39:08AM -0800, Nick Desaulniers wrote: > > On Mon, Nov 25, 2019 at 10:59 AM Dennis Zhou wrote: > > > > > > On Thu, Nov 21, 2019 at 08:27:43PM -0800, Nick Desaulniers wrote: > > > > Hi Dennis, > > > > Below is a 0day bot report from a build w/ Clang. Warning looks legit, > > > > can you please take a look? > > > > > > > > > > Ah thanks for this! Yeah that was a miss when I switched from flags -> > > > an enum and didn't update the declaration properly. I'll be sending out > > > a v4 as another fix for arm has some rebase conflicts. > > > > > > Is there a way to enable so I get these emails directly? > > > > + Rong, Philip > > > > The reports have only been sent to our mailing list where we've been > > manually triaging them. The issue with enabling them globally was > > that the script to reproduce the warning still doesn't mention how to > > build w/ Clang. > Thanks Nick for continuous caring on this. One thing we initially worry > is how to avoid duplicated reports to developer, like the one that can > be same as gcc's finding. We haven't found a way to effectively handle > this. Thanks for maintaining an invaluable tool. How would the reports be duplicated? Does 0day bot build with GCC, then rebuild with Clang? Regardless, does it matter? If I make a mistake, and get two build failure emails from 0day bot instead of one, does it matter? Sometimes developers may just get one, as some warnings are unique to each compiler. Maybe it runs the risk of folks ignoring the email if the volume is too much, but do authors generally ignore 0day bot emails? (I'd hope not). > > > > > In general the reports have been high value (I ignore most reports > > with -Wimplicit-function-declaration, which is the most frequent as it > > shows the patch was not compile tested at all). > Do we mean the report with -Wimplicit-function-declaration can be duplicated > to gcc, so we can ignore them to avoid duplication to developer? Many of the warnings GCC has Clang does as well. -Wimplicit-function-declaration is the most common warning I see in triage, which developers would see regardless of toolchain had they compiled first before pushing. It might be interesting to see maybe the intersection or common flags between GCC and Clang, and only email Clang reports for warnings unique to clang? I think CFLAGS can even be passed into make invocations so you could do: $ make CC=clang KBUILD_CFLAGS= such that any resulting warnings were unique to Clang. I'd expect such a list to quickly get stale over time though. > > > > > Rong, Philip, it's been a while since we talked about this last. Is > > there a general timeline of when these reports will be turned on > > globally? Even if the directions to reproduce aren't quite right, > For the timeline, it's not decided due to the duplication concern. We tend > to look into next year after other priorities are solved for this year. > > > generally there's enough info in the existing bugs where authors can > > rewrite their patch without even needing to rebuild with Clang (though > > having correct directions to reproduce would be nice, we could wait > > until someone asked for them explicitly). > > > > -- > > Thanks, > > ~Nick Desaulniers -- Thanks, ~Nick Desaulniers From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: multipart/mixed; boundary="===============7406093034364062561==" MIME-Version: 1.0 From: Nick Desaulniers To: kbuild-all@lists.01.org Subject: Re: [PATCH 05/22] btrfs: add the beginning of async discard, discard workqueue Date: Mon, 25 Nov 2019 17:47:00 -0800 Message-ID: In-Reply-To: <20191126014209.GB21240@intel.com> List-Id: --===============7406093034364062561== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable On Mon, Nov 25, 2019 at 5:35 PM Philip Li wrote: > > On Mon, Nov 25, 2019 at 11:39:08AM -0800, Nick Desaulniers wrote: > > On Mon, Nov 25, 2019 at 10:59 AM Dennis Zhou wrot= e: > > > > > > On Thu, Nov 21, 2019 at 08:27:43PM -0800, Nick Desaulniers wrote: > > > > Hi Dennis, > > > > Below is a 0day bot report from a build w/ Clang. Warning looks leg= it, > > > > can you please take a look? > > > > > > > > > > Ah thanks for this! Yeah that was a miss when I switched from flags -> > > > an enum and didn't update the declaration properly. I'll be sending o= ut > > > a v4 as another fix for arm has some rebase conflicts. > > > > > > Is there a way to enable so I get these emails directly? > > > > + Rong, Philip > > > > The reports have only been sent to our mailing list where we've been > > manually triaging them. The issue with enabling them globally was > > that the script to reproduce the warning still doesn't mention how to > > build w/ Clang. > Thanks Nick for continuous caring on this. One thing we initially worry > is how to avoid duplicated reports to developer, like the one that can > be same as gcc's finding. We haven't found a way to effectively handle > this. Thanks for maintaining an invaluable tool. How would the reports be duplicated? Does 0day bot build with GCC, then rebuild with Clang? Regardless, does it matter? If I make a mistake, and get two build failure emails from 0day bot instead of one, does it matter? Sometimes developers may just get one, as some warnings are unique to each compiler. Maybe it runs the risk of folks ignoring the email if the volume is too much, but do authors generally ignore 0day bot emails? (I'd hope not). > > > > > In general the reports have been high value (I ignore most reports > > with -Wimplicit-function-declaration, which is the most frequent as it > > shows the patch was not compile tested at all). > Do we mean the report with -Wimplicit-function-declaration can be duplica= ted > to gcc, so we can ignore them to avoid duplication to developer? Many of the warnings GCC has Clang does as well. -Wimplicit-function-declaration is the most common warning I see in triage, which developers would see regardless of toolchain had they compiled first before pushing. It might be interesting to see maybe the intersection or common flags between GCC and Clang, and only email Clang reports for warnings unique to clang? I think CFLAGS can even be passed into make invocations so you could do: $ make CC=3Dclang KBUILD_CFLAGS=3D such that any resulting warnings were unique to Clang. I'd expect such a list to quickly get stale over time though. > > > > > Rong, Philip, it's been a while since we talked about this last. Is > > there a general timeline of when these reports will be turned on > > globally? Even if the directions to reproduce aren't quite right, > For the timeline, it's not decided due to the duplication concern. We tend > to look into next year after other priorities are solved for this year. > > > generally there's enough info in the existing bugs where authors can > > rewrite their patch without even needing to rebuild with Clang (though > > having correct directions to reproduce would be nice, we could wait > > until someone asked for them explicitly). > > > > -- > > Thanks, > > ~Nick Desaulniers -- = Thanks, ~Nick Desaulniers --===============7406093034364062561==--