From: Stefan Wahren <stefan.wahren@i2se.com>
To: Xu Kuohai <xukuohai@huaweicloud.com>,
linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Cc: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Florian Fainelli <f.fainelli@gmail.com>,
Broadcom internal kernel review list
<bcm-kernel-feedback-list@broadcom.com>,
Maxime Ripard <maxime@cerno.tech>,
Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
Xu Kuohai <xukuohai@huawei.com>
Subject: Re: [PATCH] clk: bcm: rpi: Fix an out-of-bound access to raspberrypi_clk_variants
Date: Sat, 8 Oct 2022 19:07:24 +0200 [thread overview]
Message-ID: <bce9efac-15a8-75e5-6f3f-bc62e33d0184@i2se.com> (raw)
In-Reply-To: <20221008144544.283945-1-xukuohai@huaweicloud.com>
Hi Xu,
Am 08.10.22 um 16:45 schrieb Xu Kuohai:
> From: Xu Kuohai <xukuohai@huawei.com>
>
> KASAN reports an out-of-bound access to raspberrypi_clk_variants[]:
>
> ==================================================================
> BUG: KASAN: global-out-of-bounds in raspberrypi_clk_probe+0x1dc/0x690
> Read of size 1 at addr ffffcc7116d615a0 by task kworker/u8:0/8
>
> CPU: 1 PID: 8 Comm: kworker/u8:0 Not tainted 6.0.0-rc3-00900-g08f4df4a3c53 raspberrypi#10
this kernel is a little bit older and doesn't contain bc163555603e
("clk: bcm: rpi: Prevent out-of-bounds access").
Can you please check Linux 6.0?
Best regards
next prev parent reply other threads:[~2022-10-08 17:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-08 14:45 Xu Kuohai
2022-10-08 17:07 ` Stefan Wahren [this message]
2022-10-09 3:34 ` Xu Kuohai
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=bce9efac-15a8-75e5-6f3f-bc62e33d0184@i2se.com \
--to=stefan.wahren@i2se.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=maxime@cerno.tech \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.org \
--cc=xukuohai@huawei.com \
--cc=xukuohai@huaweicloud.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®