From: Mark Brown <broonie@kernel.org>
To: Xiaolei Wang <xiaolei.wang@windriver.com>
Cc: lgirdwood@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] regulator: pfuze100: Fix the global-out-of-bounds access in pfuze100_regulator_probe()
Date: Thu, 25 Aug 2022 12:02:28 +0100 [thread overview]
Message-ID: <YwdWxKywJXpkRC+s@sirena.org.uk> (raw)
In-Reply-To: <20220825071541.1228110-1-xiaolei.wang@windriver.com>
[-- Attachment #1: Type: text/plain, Size: 1075 bytes --]
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.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2022-08-25 11:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-25 7:15 Xiaolei Wang
2022-08-25 11:02 ` Mark Brown [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YwdWxKywJXpkRC+s@sirena.org.uk \
--to=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xiaolei.wang@windriver.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®