From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Sasha Levin <sashal@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Kees Cook <keescook@chromium.org>,
stable@vger.kernel.org, llvm@lists.linux.dev
Subject: Re: Apply 1e70212e031528918066a631c9fdccda93a1ffaa to 5.18
Date: Thu, 30 Jun 2022 13:26:32 +0200 [thread overview]
Message-ID: <Yr2IaHyNrpwnkTgo@kroah.com> (raw)
In-Reply-To: <Yrnvm6mwtaiKu6Rj@dev-arch.thelio-3990X>
On Mon, Jun 27, 2022 at 10:57:47AM -0700, Nathan Chancellor wrote:
> Hi Greg and Sasha,
>
> Please apply commit 1e70212e0315 ("hinic: Replace memcpy() with direct
> assignment") to 5.18. It fixes a warning visible when building arm64 and
> x86_64 allmodconfig with clang 14 and newer (and possibly other
> architectures but I didn't check). This will allow CONFIG_WERROR to
> remain enabled when building arm64 and x86_64 kernels with clang on 5.15
> and 5.18 (other architectures and newer versions are getting there).
>
> This change shouldn't be problematic in older kernels but the warning it
> fixes won't be visible without the new FORTIFY_SOURCE changes that
> landed in 5.18, so I wouldn't worry about backporting it further.
Now queued up, thanks.
greg k-h
prev parent reply other threads:[~2022-06-30 11:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-27 17:57 Apply 1e70212e031528918066a631c9fdccda93a1ffaa to 5.18 Nathan Chancellor
2022-06-30 11:26 ` Greg Kroah-Hartman [this message]
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=Yr2IaHyNrpwnkTgo@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=keescook@chromium.org \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=sashal@kernel.org \
--cc=stable@vger.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