From: Will Deacon <will@kernel.org>
To: "kernelci.org bot" <bot@kernelci.org>, paul@paul-moore.com
Cc: catalin.marinas@arm.com, linux-arm-kernel@lists.infradead.org,
kernel-build-reports@lists.linaro.org,
kernelci-results@groups.io
Subject: Re: arm64/for-kernelci build: 1 build: 0 failed, 1 passed, 1 warning (v6.8-rc4-55-g905b00721763)
Date: Tue, 20 Feb 2024 11:49:38 +0000 [thread overview]
Message-ID: <20240220114937.GA5545@willie-the-truck> (raw)
In-Reply-To: <65cfcc14.170a0220.b8b50.24d9@mx.google.com>
[+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-g905b00721763/
>
> 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
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-02-20 11:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-16 20:56 arm64/for-kernelci build: 1 build: 0 failed, 1 passed, 1 warning (v6.8-rc4-55-g905b00721763) kernelci.org bot
2024-02-20 11:49 ` Will Deacon [this message]
2024-02-20 14:59 ` Paul Moore
2024-02-20 15:33 ` Mark Brown
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=20240220114937.GA5545@willie-the-truck \
--to=will@kernel.org \
--cc=bot@kernelci.org \
--cc=catalin.marinas@arm.com \
--cc=kernel-build-reports@lists.linaro.org \
--cc=kernelci-results@groups.io \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=paul@paul-moore.com \
/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