* Apply 1e70212e031528918066a631c9fdccda93a1ffaa to 5.18
@ 2022-06-27 17:57 Nathan Chancellor
2022-06-30 11:26 ` Greg Kroah-Hartman
0 siblings, 1 reply; 2+ messages in thread
From: Nathan Chancellor @ 2022-06-27 17:57 UTC (permalink / raw)
To: Greg Kroah-Hartman, Sasha Levin; +Cc: Nick Desaulniers, Kees Cook, stable, llvm
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.
Cheers,
Nathan
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Apply 1e70212e031528918066a631c9fdccda93a1ffaa to 5.18
2022-06-27 17:57 Apply 1e70212e031528918066a631c9fdccda93a1ffaa to 5.18 Nathan Chancellor
@ 2022-06-30 11:26 ` Greg Kroah-Hartman
0 siblings, 0 replies; 2+ messages in thread
From: Greg Kroah-Hartman @ 2022-06-30 11:26 UTC (permalink / raw)
To: Nathan Chancellor; +Cc: Sasha Levin, Nick Desaulniers, Kees Cook, stable, llvm
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2022-06-30 11:26 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2022-06-27 17:57 Apply 1e70212e031528918066a631c9fdccda93a1ffaa to 5.18 Nathan Chancellor
2022-06-30 11:26 ` Greg Kroah-Hartman
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox