[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <YwdWxKywJXpkRC+s@sirena.org.uk>
Date: Thu, 25 Aug 2022 12:02:28 +0100
From: Mark Brown <broonie@...nel.org>
To: Xiaolei Wang <xiaolei.wang@...driver.com>
Cc: lgirdwood@...il.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] regulator: pfuze100: Fix the global-out-of-bounds access
in pfuze100_regulator_probe()
On Thu, Aug 25, 2022 at 03:15:41PM +0800, Xiaolei Wang wrote:
> This fixes the out of bounds access bug reported by KASAN.
> BUG: KASAN: global-out-of-bounds in pfuze100_regulator_probe+0x380/0x8b8
> Read of size 3968 at addr c3390640 by task swapper/0/1
>
> CPU: 0 PID: 1 Comm: swapper/0 Not tainted 6.0.0-rc1-yocto-standard+ #2
> Hardware name: Freescale i.MX6 SoloX (Device Tree)
> unwind_backtrace from show_stack+0x18/0x1c
> show_stack from dump_stack_lvl+0x68/0x90
> dump_stack_lvl from print_report+0x58/0x4c8
> print_report from kasan_report+0x7c/0x98
> kasan_report from kasan_check_range+0x20/0x170
> kasan_check_range from memcpy+0x28/0x68
Please think hard before including complete backtraces in upstream
reports, they are very large and contain almost no useful information
relative to their size so often obscure the relevant content in your
message. If part of the backtrace is usefully illustrative (it often is
for search engines if nothing else) then it's usually better to pull out
the relevant sections.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists