From: Benjamin Tissoires <bentiss@kernel.org>
To: Jiri Kosina <jikos@kernel.org>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
Arnd Bergmann <arnd@kernel.org>
Cc: "Arnd Bergmann" <arnd@arndb.de>,
"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" <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, 10 Jul 2023 10:32:40 +0200 [thread overview]
Message-ID: <168897796090.315593.7282926562695249988.b4-ty@kernel.org> (raw)
In-Reply-To: <20230705140242.844167-1-arnd@kernel.org>
On Wed, 05 Jul 2023 16:02:24 +0200, Arnd Bergmann wrote:
> A previous patch addressed the fortified memcpy warning for most
> builds, but I still see this one with gcc-9:
>
> In file included from include/linux/string.h:254,
> from drivers/hid/hid-hyperv.c:8:
> In function 'fortify_memcpy_chk',
> inlined from 'mousevsc_on_receive' at drivers/hid/hid-hyperv.c:272:3:
> include/linux/fortify-string.h:583:4: error: call to '__write_overflow_field' declared with attribute warning: detected write beyond size of field (1st parameter); maybe use struct_group()? [-Werror=attribute-warning]
> 583 | __write_overflow_field(p_size_field, size);
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> [...]
Applied to https://git.kernel.org/pub/scm/linux/kernel/git/hid/hid.git (for-6.5/upstream-fixes), thanks!
[1/1] HID: hyperv: avoid struct memcpy overrun warning
https://git.kernel.org/hid/hid/c/5f151364b1da
Cheers,
--
Benjamin Tissoires <bentiss@kernel.org>
next prev parent reply other threads:[~2023-07-10 8:33 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 [this message]
2023-07-17 9:36 ` Andy Shevchenko
2023-07-17 10:44 ` Arnd Bergmann
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=168897796090.315593.7282926562695249988.b4-ty@kernel.org \
--to=bentiss@kernel.org \
--cc=arnd@arndb.de \
--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®