Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Feedback-ID: i56a14606:Fastmail
User-Agent: Cyrus-JMAP/3.9.0-alpha0-531-gfdfa13a06d-fm-20230703.001-gfdfa13a0
Mime-Version: 1.0
Message-Id: <b0f2c4d3-c5d6-4887-b2c1-2d464c918775@app.fastmail.com>
In-Reply-To: <ZLULjoePQaF+nSk2@smile.fi.intel.com>
References: <20230705140242.844167-1-arnd@kernel.org>
 <ZLULjoePQaF+nSk2@smile.fi.intel.com>
Date:   Mon, 17 Jul 2023 12:44:01 +0200
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>,
        =?UTF-8?Q?Thomas_Wei=C3=9Fschuh?= <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
Content-Type: text/plain
Precedence: bulk

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