From: "Arnd Bergmann" <arnd@arndb.de>
To: "Andy Shevchenko" <andriy.shevchenko@intel.com>,
"Arnd Bergmann" <arnd@kernel.org>
Cc: "Jiri Kosina" <jikos@kernel.org>,
"Benjamin Tissoires" <benjamin.tissoires@redhat.com>,
"K. Y. Srinivasan" <kys@microsoft.com>,
"Haiyang Zhang" <haiyangz@microsoft.com>,
"Wei Liu" <wei.liu@kernel.org>,
"Dexuan Cui" <decui@microsoft.com>,
"Paulo Miguel Almeida" <paulo.miguel.almeida.rodenas@gmail.com>,
"Michael Kelley (LINUX)" <mikelley@microsoft.com>,
"Dawei Li" <set_pte_at@outlook.com>,
"Yang Yingliang" <yangyingliang@huawei.com>,
"Thomas Weißschuh" <linux@weissschuh.net>,
linux-hyperv@vger.kernel.org, linux-input@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] HID: hyperv: avoid struct memcpy overrun warning
Date: Mon, 17 Jul 2023 12:44:01 +0200 [thread overview]
Message-ID: <b0f2c4d3-c5d6-4887-b2c1-2d464c918775@app.fastmail.com> (raw)
In-Reply-To: <ZLULjoePQaF+nSk2@smile.fi.intel.com>
On Mon, Jul 17, 2023, at 11:36, Andy Shevchenko wrote:
> On Wed, Jul 05, 2023 at 04:02:24PM +0200, Arnd Bergmann wrote:
>> From: Arnd Bergmann <arnd@arndb.de>
>>
>> A previous patch addressed the fortified memcpy warning for most
>> builds, but I still see this one with gcc-9:
>
> JFYI: as of today I have run Linux Next with `make W=1 allmodconfig` on x86_64
> and it seems there are still tons of similar issues which break the build.
It's a bit more complex:
- yes, there are lots of warnings for memcpy() read overflow when you
build allmodconfig kernels with W=1. I have patches for all of these and
plan to submit them over time.
- This particular one is a memcpy /write/ overflow, i.e. the
destination type overflows with the length according to gcc's
understanding of the structures. This warning is enabled even
without W=1, though it may only show up in certain configurations
or compiler versions.
Arnd
prev parent reply other threads:[~2023-07-17 10:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-05 14:02 Arnd Bergmann
2023-07-08 14:37 ` Michael Kelley (LINUX)
2023-07-10 8:32 ` Benjamin Tissoires
2023-07-17 9:36 ` Andy Shevchenko
2023-07-17 10:44 ` Arnd Bergmann [this message]
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=b0f2c4d3-c5d6-4887-b2c1-2d464c918775@app.fastmail.com \
--to=arnd@arndb.de \
--cc=andriy.shevchenko@intel.com \
--cc=arnd@kernel.org \
--cc=benjamin.tissoires@redhat.com \
--cc=decui@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=jikos@kernel.org \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=mikelley@microsoft.com \
--cc=paulo.miguel.almeida.rodenas@gmail.com \
--cc=set_pte_at@outlook.com \
--cc=wei.liu@kernel.org \
--cc=yangyingliang@huawei.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
all inboxes | Powered by JetHome®