From: Jakub Kicinski <kuba@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Nathan Chancellor <nathan@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Borislav Petkov <bp@suse.de>,
"the arch/x86 maintainers" <x86@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Josh Poimboeuf <jpoimboe@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
clang-built-linux <llvm@lists.linux.dev>,
stable <stable@vger.kernel.org>,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH v2] x86/speculation: Use DECLARE_PER_CPU for x86_spec_ctrl_current
Date: Thu, 14 Jul 2022 15:18:45 -0700 [thread overview]
Message-ID: <20220714151845.59905190@kernel.org> (raw)
In-Reply-To: <CAHk-=wgqJFV45497fBfc1HS3Oaoqi3pfenZ0XM3uqFGYz8wTQQ@mail.gmail.com>
On Thu, 14 Jul 2022 15:14:53 -0700 Linus Torvalds wrote:
> On Thu, Jul 14, 2022 at 2:56 PM Jakub Kicinski <kuba@kernel.org> wrote:
> > I have clang 13, let me double check this fix is enough for the build
> > to complete without disabling WERROR.
>
> I have clang 14 locally, and it builds fine with that (and doesn't
> build without it).
FWIW I can confirm - builds with clang 13 as well.
> I actually normally build the kernel with both gcc and clang. My
> "upstream" kernel I build with gcc, and then I have my "private random
> collection of patches" kernel that I build with clang and that are
> just rebased on top of the kernel-of-the-day.
>
> This is all entirely for historical reasons - part of my "private
> random collection of patches" used to be the "asm goto with outputs",
> which had clang support first.
>
> But then the reason I never even noticed the build breakage with the
> retbleed patches until much too late was that those I just had as a
> third fork off my upstream kernel, so despite me usually building with
> clang too, that only got attention from gcc.
>
> So it's really just a microcosm version of the exact same bigger issue
> we always have with those embargoed hw security patches: they end up
> missing out on all the usual test environments.
>
> Anyway, I cherry-picked Nathan's patch from my clang tree and pushed
> it out as commit db886979683a ("x86/speculation: Use DECLARE_PER_CPU
> for x86_spec_ctrl_current").
Awesome, thanks!
next prev parent reply other threads:[~2022-07-14 22:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-13 15:24 [PATCH v2] x86/speculation: Use DECLARE_PER_CPU for x86_spec_ctrl_current Nathan Chancellor
2022-07-13 15:36 ` Nick Desaulniers
2022-07-13 16:22 ` Peter Zijlstra
2022-07-13 16:27 ` Nathan Chancellor
2022-07-14 13:36 ` [tip: x86/urgent] " tip-bot2 for Nathan Chancellor
2022-07-14 21:30 ` [PATCH v2] " Jakub Kicinski
2022-07-14 21:51 ` Linus Torvalds
2022-07-14 21:56 ` Linus Torvalds
2022-07-14 22:11 ` Peter Zijlstra
2022-07-14 21:56 ` Jakub Kicinski
2022-07-14 22:14 ` Linus Torvalds
2022-07-14 22:18 ` Jakub Kicinski [this message]
2022-07-15 16:00 ` Borislav Petkov
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=20220714151845.59905190@kernel.org \
--to=kuba@kernel.org \
--cc=bp@suse.de \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=peterz@infradead.org \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox