From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Gabriel Francisco <frc.gabriel@gmail.com>
Cc: Isaac Manjarres <isaacmanjarres@google.com>,
Saravana Kannan <saravanak@google.com>,
patches@armlinux.org.uk, Guenter Roeck <linux@roeck-us.net>,
kernel-team@android.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] amba: Fix use-after-free in amba_read_periphid()
Date: Tue, 6 Sep 2022 22:27:25 +0100 [thread overview]
Message-ID: <Yxe7PQR4/s4MlvYE@shell.armlinux.org.uk> (raw)
In-Reply-To: <0d2875d6-280f-c901-a7b4-92ea6a84e966@gmail.com>
On Tue, Sep 06, 2022 at 10:58:55PM +0200, Gabriel Francisco wrote:
> I'm afraid the issue is still showing up (looks similar when I tested with
> 6.0-rc2 + your patch and it went away when combining with Zhen Lei's one).
>
> I added the dmesg log at
> https://bugzilla.kernel.org/attachment.cgi?id=301756
Bugzilla's all great and all, but not with firefox. Firefox wants me
to open that attachment in Libreoffice Writer... so wget -O - ... |less
to the rescue.
So you have an oops in __clk_put(), which suggests you don't have
"amba: Fix use-after-free in amba_read_periphid()" from Isaac Manjarres
applied. I haven't sent it upstream yet, but even if I had, 6.0-rc2
would be too old. Please try with Isaac's patch applied, thanks.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
prev parent reply other threads:[~2022-09-06 21:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 17:28 [PATCH v2] amba: Fix use-after-free in amba_read_periphid() Isaac J. Manjarres
2022-08-25 22:24 ` Saravana Kannan
2022-08-30 5:30 ` Guenter Roeck
2022-09-04 11:15 ` Gabriel Francisco
2022-09-06 17:54 ` Isaac Manjarres
2022-09-06 20:58 ` Gabriel Francisco
2022-09-06 21:27 ` Russell King (Oracle) [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=Yxe7PQR4/s4MlvYE@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=frc.gabriel@gmail.com \
--cc=isaacmanjarres@google.com \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=patches@armlinux.org.uk \
--cc=saravanak@google.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