From: Robin Murphy <robin.murphy@arm.com>
To: Stephan Gerhold <stephan@gerhold.net>
Cc: Brian Masney <masneyb@onstation.org>,
robdclark@gmail.com, bjorn.andersson@linaro.org, joro@8bytes.org,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
j.neuschaefer@gmx.net, iommu@lists.linux-foundation.org,
agross@kernel.org, Naresh Kamboju <naresh.kamboju@linaro.org>
Subject: Re: [PATCH v2] iommu/qcom: fix NULL pointer dereference during probe deferral
Date: Tue, 18 Feb 2020 14:27:20 +0000 [thread overview]
Message-ID: <4ed8542a-40fe-ae34-4203-efbcf285d784@arm.com> (raw)
In-Reply-To: <20200218120435.GA152723@gerhold.net>
On 18/02/2020 12:04 pm, Stephan Gerhold wrote:
[...]
> Are you going to send a patch for the diff below?
> AFAICT this problem still exists in 5.6-rc2.
>
> Your patch also seems to fix a warning during probe deferral on arm64
> that has been around for quite a while. (At least for me...)
>
> (See https://lore.kernel.org/linux-iommu/CA+G9fYtScOpkLvx=__gP903uJ2v87RwZgkAuL6RpF9_DTDs9Zw@mail.gmail.com/)
Ha, I did see that and vaguely remembered a discussion about that
warning logic being broken, but I'd totally forgotten I was involved to
that extent :)
Luckily I've managed to track the diff down in my Git stash, so I'll
write it up properly - thanks for the reminder!
Robin.
prev parent reply other threads:[~2020-02-18 14:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-04 0:20 [PATCH v2] iommu/qcom: fix NULL pointer dereference during probe deferral Brian Masney
2020-01-06 13:26 ` Robin Murphy
2020-01-07 11:55 ` Brian Masney
2020-02-18 12:04 ` Stephan Gerhold
2020-02-18 14:27 ` Robin Murphy [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=4ed8542a-40fe-ae34-4203-efbcf285d784@arm.com \
--to=robin.murphy@arm.com \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=iommu@lists.linux-foundation.org \
--cc=j.neuschaefer@gmx.net \
--cc=joro@8bytes.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masneyb@onstation.org \
--cc=naresh.kamboju@linaro.org \
--cc=robdclark@gmail.com \
--cc=stephan@gerhold.net \
/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