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
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
linux-stable-mirror@lists.linaro.org
-
Greg Kroah-Hartman -
Nathan Chancellor