[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20201118150201.7orvzppzd4rikg3m@shrine>
Date: Wed, 18 Nov 2020 09:02:01 -0600
From: Nishanth Menon <nm@...com>
To: Arnd Bergmann <arnd@...nel.org>
CC: Naresh Kamboju <naresh.kamboju@...aro.org>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>,
Linux-Next Mailing List <linux-next@...r.kernel.org>,
open list <linux-kernel@...r.kernel.org>,
linux-mm <linux-mm@...ck.org>, <lkft-triage@...ts.linaro.org>,
linux-mmc <linux-mmc@...r.kernel.org>,
Linus Walleij <linus.walleij@...aro.org>,
Arnd Bergmann <arnd@...db.de>,
Andrew Morton <akpm@...ux-foundation.org>,
Steven Rostedt <rostedt@...dmis.org>,
Ulf Hansson <ulf.hansson@...aro.org>,
Linux-OMAP <linux-omap@...r.kernel.org>,
Liam Girdwood <lgirdwood@...il.com>,
Mark Brown <broonie@...nel.org>
Subject: Re: [arm] BUG: KASAN: slab-out-of-bounds in memcmp+0x30/0x5c
On 09:14-20201118, Arnd Bergmann wrote:
> On Wed, Nov 18, 2020 at 12:24 AM Nishanth Menon <nm@...com> wrote:
> > On 16:25-20201117, Arnd Bergmann wrote:
> >
> > Yes, this was indeed a bug that has been around for some time now :(
> >
> > I tested with a variant of the above (did'nt like that
> > oinfo was being assigned an invalid address)
> > Boot log: https://pastebin.ubuntu.com/p/nZfz3HF8N6/ (with the same
> > config as in the report): Would you prefer to me to send the following
> > as a formal patch?
>
> Awesome, thanks for the new patch and testing it!
>
> Yes, please send this as a proper patch to have it picked up
> into the regulator tree as a bugfix.
>
> Reported-by: Naresh Kamboju <naresh.kamboju@...aro.org>
> Reviewed-by: Arnd Bergmann <arnd@...db.de>
Done. And thanks for the triage, Arnd.
https://patchwork.kernel.org/project/linux-omap/patch/20201118145009.10492-1-nm@ti.com/
Naresh,
Thanks for reporting the bug. That was an ancient one.. Glad we
could find it.
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
Powered by blists - more mailing lists