LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Gustavo A. R. Silva" <gustavoars@kernel.org>,
Kees Cook <keescook@chromium.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Masahiro Yamada <masahiroy@kernel.org>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
clang-built-linux <clang-built-linux@googlegroups.com>
Subject: Re: [PATCH] kbuild: Enable -Wimplicit-fallthrough for clang 14.0.0+
Date: Mon, 16 Aug 2021 21:55:28 -0700 [thread overview]
Message-ID: <5c856f36-69a7-e274-f72a-c3aef195adeb@kernel.org> (raw)
In-Reply-To: <CAHk-=wgFXOf9OUh3+vmWjhp1PC47RVsUkL0NszBxSWhbGzx4tw@mail.gmail.com>
On 8/16/2021 9:37 PM, Linus Torvalds wrote:
> On Mon, Aug 16, 2021 at 6:20 PM Nathan Chancellor <nathan@kernel.org> wrote:
>>
>> Additionally, there should be some time for the CI systems to update
>> their clang-14 builds, as the recent 0day report shows.
>
> What?
>
> No, the 0day report shows that the patch is buggy, and that the
>
> ifeq ($(shell test $(CONFIG_CLANG_VERSION) -ge 140000; echo $$?),0)
>
> clearly doesn't work at all, since the flag is enabled on those
> systems with old clang versions.
>
> Alternatively, the test works, but the 140000 version is not enough.
So technically speaking, the 140000 is not enough at this very moment
for the fact that there are certain systems that test with clang-14
builds that do not have my clang patch in it yet; however, those systems
do update clang regularly (the 0day version is just seven hours old at
the time of writing this) so they will have a version that contains my
patch shortly, making the check work just fine. We have done this in the
past with checks that are gated on clang versions that are in
development, with the expectation that if someone is using a development
release of clang, they are keeping it up to date so that they get fixes
that we push there; otherwise, it is just better to stick with the
release branches.
> So no. This patch is simply completely wrong, and doesn't fix the
> problem with Clang's buggy -Wimplicit-fallthrough flag.
If you/Gustavo would prefer, I can upgrade that check to
ifneq ($(call cc-option, -Wunreachable-code-fallthrough),)
I was just trying to save a call to the compiler, as that is more
expensive than a shell test call.
Cheers,
Nathan
next prev parent reply other threads:[~2021-08-17 4:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-17 0:56 Nathan Chancellor
2021-08-17 4:16 ` kernel test robot
2021-08-17 4:20 ` Nathan Chancellor
2021-08-17 4:37 ` Linus Torvalds
2021-08-17 4:55 ` Nathan Chancellor [this message]
2021-08-17 18:03 ` Kees Cook
2021-08-17 18:25 ` Nathan Chancellor
2021-08-17 21:17 ` Masahiro Yamada
2021-08-17 21:33 ` Gustavo A. R. Silva
2021-08-17 23:06 ` Kees Cook
2021-08-17 23:23 ` Nathan Chancellor
2021-08-17 23:40 ` Gustavo A. R. Silva
2021-08-18 4:15 ` Masahiro Yamada
2021-08-18 4:27 ` Philip Li
2021-08-18 4:45 ` Gustavo A. R. Silva
2021-08-18 7:31 ` Philip Li
2021-08-18 12:12 ` Mark Brown
2021-08-25 21:09 ` Nick Desaulniers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5c856f36-69a7-e274-f72a-c3aef195adeb@kernel.org \
--to=nathan@kernel.org \
--cc=clang-built-linux@googlegroups.com \
--cc=gustavoars@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=ndesaulniers@google.com \
--cc=torvalds@linux-foundation.org \
--subject='Re: [PATCH] kbuild: Enable -Wimplicit-fallthrough for clang 14.0.0+' \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).