[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+fCnZd2G5Zm4tcW1qTEHrzDAM=K6apCSftYKgLMETJ4FBGNAA@mail.gmail.com>
Date: Wed, 24 Jul 2024 00:20:25 +0200
From: Andrey Konovalov <andreyknvl@...il.com>
To: kernel test robot <oliver.sang@...el.com>
Cc: oe-lkp@...ts.linux.dev, lkp@...el.com, linux-kernel@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>, Erhard Furtner <erhard_f@...lbox.org>,
Nico Pache <npache@...hat.com>, Marco Elver <elver@...gle.com>,
Alexander Potapenko <glider@...gle.com>, Andrey Ryabinin <ryabinin.a.a@...il.com>,
Daniel Axtens <dja@...ens.net>, Dmitry Vyukov <dvyukov@...gle.com>, linux-hardening@...r.kernel.org
Subject: Re: [linus:master] [kasan, fortify] 2e577732e8: BUG:KASAN:global-out-of-bounds_in_usb_copy_descriptors
On Tue, Jul 23, 2024 at 10:51 AM kernel test robot
<oliver.sang@...el.com> wrote:
>
> Hello,
>
> we noticed this is a fix commit, however, we don't have enough knowledge to
> determine if new KASAN issue is expected actually after this fix.
> so we just made this report FYI what we observed in our tests.
>
>
> kernel test robot noticed "BUG:KASAN:global-out-of-bounds_in_usb_copy_descriptors" on:
>
> commit: 2e577732e8d28b9183df701fb90cb7943aa4ed16 ("kasan, fortify: properly rename memintrinsics")
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
Hi,
Yes, that patch might uncover new bugs that previously were not
detectable. There's still a chance that something is wrong with KASAN
and it reports a false positive, but most likely, this report is a
real issue.
Thank you!
Powered by blists - more mailing lists