From: Jakub Kicinski <kuba@kernel.org>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
Kees Cook <keescook@chromium.org>,
Nick Desaulniers <ndesaulniers@google.com>,
"David S. Miller" <davem@davemloft.net>,
Paolo Abeni <pabeni@redhat.com>, Netdev <netdev@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: mainline build failure due to 281d0c962752 ("fortify: Add Clang support")
Date: Wed, 22 Jun 2022 11:07:33 -0700 [thread overview]
Message-ID: <20220622110733.1eba089c@kernel.org> (raw)
In-Reply-To: <YrMu5bdhkPzkxv/X@dev-arch.thelio-3990X>
On Wed, 22 Jun 2022 08:01:57 -0700 Nathan Chancellor wrote:
> On Wed, Jun 22, 2022 at 08:47:22AM -0500, Linus Torvalds wrote:
> > On Wed, Jun 22, 2022 at 5:23 AM Sudip Mukherjee
> > <sudipm.mukherjee@gmail.com> wrote:
> > >
> > > I have recently (since yesterday) started building the mainline kernel
> > > with clang-14 and I am seeing a build failure with allmodconfig.
>
> Right, this is known. Kees sent a fix for that warning recently but it
> went to net-next instead of net it seems:
>
> https://git.kernel.org/netdev/net-next/c/2c0ab32b73cfe39a609192f338464e948fc39117
>
> I am not sure if that change could be cherry-picked or applied to net so
> that it could be fixed in mainline, I see the netdev maintainers are
> already on CC so maybe they can comment on that?
Sorry about the hassle, done now. It's commit 1e70212e0315 ("hinic:
Replace memcpy() with direct assignment") in net and should make it
to Linus tomorrow.
next prev parent reply other threads:[~2022-06-22 18:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-22 10:23 mainline build failure due to 281d0c962752 ("fortify: Add Clang support") Sudip Mukherjee
2022-06-22 13:47 ` Linus Torvalds
2022-06-22 15:01 ` Nathan Chancellor
2022-06-22 16:21 ` Linus Torvalds
2022-06-22 17:26 ` Sudip Mukherjee
2022-06-22 17:48 ` Linus Torvalds
2022-06-22 22:40 ` Nick Desaulniers
2022-06-23 10:12 ` David Laight
2022-06-23 23:33 ` Nick Desaulniers
2022-06-28 22:42 ` Josh Poimboeuf
2022-06-29 16:08 ` Linus Torvalds
2022-06-29 16:34 ` Josh Poimboeuf
2022-06-29 21:21 ` Nick Desaulniers
2022-06-29 21:39 ` Linus Torvalds
2022-06-22 18:07 ` Jakub Kicinski [this message]
2022-06-22 15:08 ` Sudip Mukherjee
2022-06-22 15:19 ` Linus Torvalds
2022-06-22 16:00 ` Sudip Mukherjee
2022-06-22 16:07 ` Linus Torvalds
2022-06-22 16:16 ` Sudip Mukherjee
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=20220622110733.1eba089c@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sudipm.mukherjee@gmail.com \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.