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.4 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,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 5BB7AC432C0 for ; Mon, 25 Nov 2019 19:39:22 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 330532075C for ; Mon, 25 Nov 2019 19:39:22 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=google.com header.i=@google.com header.b="G/S6X4qW" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726504AbfKYTjV (ORCPT ); Mon, 25 Nov 2019 14:39:21 -0500 Received: from mail-pj1-f65.google.com ([209.85.216.65]:34365 "EHLO mail-pj1-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725823AbfKYTjV (ORCPT ); Mon, 25 Nov 2019 14:39:21 -0500 Received: by mail-pj1-f65.google.com with SMTP id bo14so7056730pjb.1 for ; Mon, 25 Nov 2019 11:39:20 -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=7MBxWDkXpERqkSDmMhodvqUg0A3hHgxZWxKtcdO3owk=; b=G/S6X4qW+KCWwWsTZ30hKhGDTXPozUY6KO/wTOF/NqESVUfZHxKMK73KWqEolwpFfX lKSB+c+FzIJBcLbOSNo46LFaDsPdEoEciWzAftJwOAEQ2ulyPRkuaeezuodFmgV1t6Yx n9PI8sBPYl9WSdpuCSMFL4nosfJNY5xmX8OI840P6tOaKB4R2yzAWwT1ja1uNK/nLJ88 tlE47Lw9vZXQehP24l+aL1+TrKflLmdA8qtiMp18GH3qj1FI37PSo8ki07agaWKcQOWF QA3O/YYkgC5Dse0/r0itGSnTzPZDCESmxCIVh3jBGU00aJleVObXdq9iMF8juutD+Wtv Fq4w== 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=7MBxWDkXpERqkSDmMhodvqUg0A3hHgxZWxKtcdO3owk=; b=RozPS2IixK95SFjlzWtcj2+/MXO/PfZs5OrWeVaftt5iALT4yOk3JKsJ50tivOqdcI LPtEnwNntwzXZy3agqv69hPbKgxCpGWQVvOT6IZJ6JThPEFOkpLDbOFjqgfumR7iImUs 3D4JYxySwqAZG5kx3cXR9sH5Tb217fCdHx0UDG9LNhiNpjUvnYNGJZptv0D9d0XFTLzy rp/u41g1BUDkodrzmU6uEhoSuK8hwspUn0Vbyzk2nvXW8GJLBXJsw3RpW7XwaYE+rpJA 7b4zU8sw3bZgcndhoCPiuviAoCIXML5vky0MswLQpHvFF1bFbEWXDnLcEzCtWxAwdJfe +CtA== X-Gm-Message-State: APjAAAWZoKZni6kuwKo6ahQAC+4nRvZWwNCD/5hTFtlDPtpNaWL95oIj l4YaCU3ZqejcWsQRrNLLxcSlOZE/Ymyg7qlS3w7Grw== X-Google-Smtp-Source: APXvYqx0q4HEgjD9JrP4AWKwnmjTpmQfvZt9298pmTr4dcYXx0tuesGY7w6SO8LAaYOR3ISzbub2FdLnmwHNpUQZsz0= X-Received: by 2002:a17:902:8498:: with SMTP id c24mr29731936plo.223.1574710759582; Mon, 25 Nov 2019 11:39:19 -0800 (PST) MIME-Version: 1.0 References: <201911220351.HPI9gxNo%lkp@intel.com> <20191125185931.GA30548@dennisz-mbp.dhcp.thefacebook.com> In-Reply-To: <20191125185931.GA30548@dennisz-mbp.dhcp.thefacebook.com> From: Nick Desaulniers Date: Mon, 25 Nov 2019 11:39:08 -0800 Message-ID: Subject: Re: [PATCH 05/22] btrfs: add the beginning of async discard, discard workqueue To: Dennis Zhou , Chen Rong , Philip Li Cc: 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 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. 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). 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, 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