[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <fb5dc931-e97f-4e4b-83c4-06488f083c1e@app.fastmail.com>
Date: Tue, 18 Feb 2025 07:04:29 +0100
From: "Arnd Bergmann" <arnd@...db.de>
To: "kernel test robot" <oliver.sang@...el.com>
Cc: "Philip Li" <philip.li@...el.com>,
"Elizabeth Figura" <zfigura@...eweavers.com>,
"kernel test robot" <lkp@...el.com>, oe-kbuild-all@...ts.linux.dev,
linux-kernel@...r.kernel.org
Subject: Re: include/linux/thread_info.h:259:25: error: call to '__bad_copy_to'
declared with attribute error: copy destination size is too small
On Tue, Feb 18, 2025, at 03:44, Oliver Sang wrote:
> On Fri, Feb 14, 2025 at 12:22:33PM +0100, Arnd Bergmann wrote:
>> On Fri, Feb 14, 2025, at 09:44, Philip Li wrote:
>> > On Mon, Feb 10, 2025 at 02:39:46PM -0600, Elizabeth Figura wrote:
>>
>> Maybe the change below would address it? (Not sure I handled the
>> "+1" right here, but something like that should make it obvious
>> to the compiler what the check is).
>
> yes, below change fixed the build error we reported. thanks
>
> Tested-by: kernel test robot <oliver.sang@...el.com>
Thanks for testing!
Elizabeth, can you turn this into a proper patch with
"Suggested-by: Arnd Bergmann <arnd@...db.de>"? I assume
you'll want to make some slight changes to ensure it's
both readable and correct, but apparently calculating
the size in bytes and do both the range checking and
the copy based on that is what makes gcc see the limit
correctly.
Arnd
Powered by blists - more mailing lists