mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Gabriel Francisco <frc.gabriel@gmail.com>
To: Isaac Manjarres <isaacmanjarres@google.com>
Cc: Russell King <linux@armlinux.org.uk>,
	Saravana Kannan <saravanak@google.com>,
	"Russell King (Oracle)" <rmk+kernel@armlinux.org.uk>,
	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:58:55 +0200	[thread overview]
Message-ID: <0d2875d6-280f-c901-a7b4-92ea6a84e966@gmail.com> (raw)
In-Reply-To: <CABfwK12ChYDmhvR2EO1q2NUS4Zhd1WO8UWWoSVNY331wwbKS0w@mail.gmail.com>

On 06/09/2022 19:54, Isaac Manjarres wrote:
> On Sun, Sep 4, 2022 at 4:15 AM Gabriel Francisco <frc.gabriel@gmail.com> wrote:
>> This patch alone on top of v6.0-rc2 still gives me the null pointer.
>>
>> But combining it with Zhen Lei's patch (from
>> https://lkml.org/lkml/2022/8/27/164) my device boots successfully.
> Hi Gabriel,
>
> Thanks for your e-mail. I think my AMBA bus patch and
> https://lore.kernel.org/all/20220817184026.3468620-1-isaacmanjarres@google.com/
> (merged in 6.0-rc4), instead of Zhen Lei's patch, should fix the
> problem entirely.
>
> Thanks,
> Isaac

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

Thank you,

Gabriel Francisco



  reply	other threads:[~2022-09-06 20:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-18 17:28 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 [this message]
2022-09-06 21:27       ` Russell King (Oracle)

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=0d2875d6-280f-c901-a7b4-92ea6a84e966@gmail.com \
    --to=frc.gabriel@gmail.com \
    --cc=isaacmanjarres@google.com \
    --cc=kernel-team@android.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=linux@roeck-us.net \
    --cc=patches@armlinux.org.uk \
    --cc=rmk+kernel@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
all inboxes | Powered by JetHome®