arm64/for-kernelci build: 1 build: 0 failed, 1 passed, 1 warning (v6.8-rc4-55-g905b00721763)
arm64/for-kernelci build: 1 build: 0 failed, 1 passed, 1 warning (v6.8-rc4-55-g905b00721763)
Full Build Summary: https://kernelci.org/build/arm64/branch/for-kernelci/kernel/v6.8-rc4-55-g905...
Tree: arm64 Branch: for-kernelci Git Describe: v6.8-rc4-55-g905b00721763 Git Commit: 905b007217637b34a6a877271f21ed0dada0f564 Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git Built: 1 unique architecture
Warnings Detected:
arm64: defconfig (gcc-10): 1 warning
Warnings summary:
1 security/security.c:810:2: warning: ‘memcpy’ offset 32 is out of the bounds [0, 0] [-Warray-bounds]
================================================================================
Detailed per-defconfig build reports:
-------------------------------------------------------------------------------- defconfig (arm64, gcc-10) — PASS, 0 errors, 1 warning, 0 section mismatches
Warnings: security/security.c:810:2: warning: ‘memcpy’ offset 32 is out of the bounds [0, 0] [-Warray-bounds]
--- For more info write to info@kernelci.org
[+Paul Moore for the array bounds warning]
On Fri, Feb 16, 2024 at 12:56:52PM -0800, kernelci.org bot wrote:
arm64/for-kernelci build: 1 build: 0 failed, 1 passed, 1 warning (v6.8-rc4-55-g905b00721763)
Full Build Summary: https://kernelci.org/build/arm64/branch/for-kernelci/kernel/v6.8-rc4-55-g905...
Tree: arm64 Branch: for-kernelci Git Describe: v6.8-rc4-55-g905b00721763 Git Commit: 905b007217637b34a6a877271f21ed0dada0f564 Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git Built: 1 unique architecture
Warnings Detected:
arm64: defconfig (gcc-10): 1 warning
Warnings summary:
1 security/security.c:810:2: warning: ‘memcpy’ offset 32 is out of the bounds [0, 0] [-Warray-bounds]================================================================================
Detailed per-defconfig build reports:
defconfig (arm64, gcc-10) — PASS, 0 errors, 1 warning, 0 section mismatches
Warnings: security/security.c:810:2: warning: ‘memcpy’ offset 32 is out of the bounds [0, 0] [-Warray-bounds]
Paul, sorry if you've had lots of these reports already, but this one keeps showing up in our CI and I don't think it's related to any of our arm64 changes. So, on the off chance that you're not aware, here it is!
Will
On Tue, Feb 20, 2024 at 6:49 AM Will Deacon will@kernel.org wrote:
[+Paul Moore for the array bounds warning]
On Fri, Feb 16, 2024 at 12:56:52PM -0800, kernelci.org bot wrote:
arm64/for-kernelci build: 1 build: 0 failed, 1 passed, 1 warning (v6.8-rc4-55-g905b00721763)
Full Build Summary: https://kernelci.org/build/arm64/branch/for-kernelci/kernel/v6.8-rc4-55-g905...
Tree: arm64 Branch: for-kernelci Git Describe: v6.8-rc4-55-g905b00721763 Git Commit: 905b007217637b34a6a877271f21ed0dada0f564 Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git Built: 1 unique architecture
Warnings Detected:
arm64: defconfig (gcc-10): 1 warning
Warnings summary:
1 security/security.c:810:2: warning: ‘memcpy’ offset 32 is out of the bounds [0, 0] [-Warray-bounds]================================================================================
Detailed per-defconfig build reports:
defconfig (arm64, gcc-10) — PASS, 0 errors, 1 warning, 0 section mismatches
Warnings: security/security.c:810:2: warning: ‘memcpy’ offset 32 is out of the bounds [0, 0] [-Warray-bounds]
Paul, sorry if you've had lots of these reports already, but this one keeps showing up in our CI and I don't think it's related to any of our arm64 changes. So, on the off chance that you're not aware, here it is!
Hi Will,
Yes, I've seen this reported quite a bit and I've double (triple ...) checked that it is a bogus warning. Kees mentioned that it was due to a known gcc bug so I've been ignoring it, I would appreciate it if you could do the same. I love to see bugs reported during the development cycle - thanks for your help in this regard! - but I do get tired of seeing the same bogus warnings caused by a buggy toolchain.
On Tue, Feb 20, 2024 at 09:59:23AM -0500, Paul Moore wrote:
Yes, I've seen this reported quite a bit and I've double (triple ...) checked that it is a bogus warning. Kees mentioned that it was due to a known gcc bug so I've been ignoring it, I would appreciate it if you could do the same. I love to see bugs reported during the development cycle - thanks for your help in this regard! - but I do get tired of seeing the same bogus warnings caused by a buggy toolchain.
Note that the toolchain concerned is the Debian one (oldstable now, we should be upgrading soonish but I don't know about other users) rather than something obscure and custom.
kernel-build-reports@lists.linaro.org
-
kernelci.org bot -
Mark Brown -
Paul Moore -
Will Deacon