From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: linux-stable <stable@vger.kernel.org>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
lkft-triage@lists.linaro.org, X86 ML <x86@kernel.org>,
Shuah Khan <shuah@kernel.org>, Andy Lutomirski <luto@kernel.org>,
Dave Hansen <dave.hansen@linux.intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Jann Horn <jannh@google.com>, John Hubbard <jhubbard@nvidia.com>,
Andrew Morton <akpm@linux-foundation.org>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Anders Roxell <anders.roxell@linaro.org>
Subject: Re: test_vsyscall.c:500:22: warning: '__builtin_memcmp_eq' specified bound 4096 exceeds source size 0
Date: Thu, 6 Jan 2022 10:32:31 +0100 [thread overview]
Message-ID: <Yda3L0givFBDZtXs@kroah.com> (raw)
In-Reply-To: <CA+G9fYvUu9+68mkCT0S8L0gL28jc5MXGQqOGH6ObciK72FbD8A@mail.gmail.com>
On Thu, Jan 06, 2022 at 02:55:53PM +0530, Naresh Kamboju wrote:
> While building selftests the following warnings were noticed for x86_64
> architecture on Linux stable v5.15.13 kernel.
>
> metadata:
> git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
> git commit: 734eb1fd2073f503f5c6b44f1c0d453ca6986b84
> git describe: v5.15.13
> toolchain": gcc-11
> kernel-config: https://builds.tuxbuild.com/23HFo8abXIL6i4FFfSYiJlqAYMW/config
>
> x86_64-linux-gnu-gcc -m64 -o \
> /home/tuxbuild/.cache/tuxmake/builds/current/kselftest/x86/test_vsyscall_64 \
> -O2 -g -std=gnu99 -pthread -Wall -no-pie \
> -DCAN_BUILD_64 test_vsyscall.c helpers.h -lrt -ldl
>
> test_vsyscall.c: In function 'test_process_vm_readv':
> test_vsyscall.c:500:22: warning: '__builtin_memcmp_eq' specified bound
> 4096 exceeds source size 0 [-Wstringop-overread]
> 500 | if (!memcmp(buf, (const void
> *)0xffffffffff600000, 4096)) {
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
>
> Build link:
> https://builds.tuxbuild.com/23HFo8abXIL6i4FFfSYiJlqAYMW/
>
> # To install tuxmake on your system globally:
> # sudo pip3 install -U tuxmake
>
> tuxmake --runtime podman --target-arch x86_64 --toolchain gcc-11 \
> --kconfig https://builds.tuxbuild.com/23HFo8abXIL6i4FFfSYiJlqAYMW/config \
> cpupower headers kernel kselftest kselftest-merge modules
Is this a new regression from 5.15.0? Is it also present on Linus's tree?
thanks,
greg k-h
next prev parent reply other threads:[~2022-01-06 9:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-06 9:25 test_vsyscall.c:500:22: warning: '__builtin_memcmp_eq' specified bound 4096 exceeds source size 0 Naresh Kamboju
2022-01-06 9:32 ` Greg Kroah-Hartman [this message]
2022-01-06 9:49 ` Naresh Kamboju
2022-01-06 10:05 ` Greg Kroah-Hartman
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=Yda3L0givFBDZtXs@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=anders.roxell@linaro.org \
--cc=dave.hansen@linux.intel.com \
--cc=jannh@google.com \
--cc=jhubbard@nvidia.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=luto@kernel.org \
--cc=naresh.kamboju@linaro.org \
--cc=peterz@infradead.org \
--cc=shuah@kernel.org \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).