From: Will Deacon <will.deacon@arm.com>
To: Artem Savkov <asavkov@redhat.com>
Cc: Vivek Gautam <vivek.gautam@codeaurora.org>,
linux-arm-kernel@lists.infradead.org,
iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iommu/arm-smmu: fix null-pointer dereference in arm_smmu_add_device
Date: Tue, 8 Aug 2017 10:26:14 +0100 [thread overview]
Message-ID: <20170808092614.GB12887@arm.com> (raw)
In-Reply-To: <1502182681-8966-1-git-send-email-asavkov@redhat.com>
Hi Artem,
Thanks for the patch.
On Tue, Aug 08, 2017 at 10:58:01AM +0200, Artem Savkov wrote:
> Commit c54451a "iommu/arm-smmu: Fix the error path in arm_smmu_add_device"
> removed fwspec assignment in legacy_binding path as redundant which is
> wrong. It needs to be updated after fwspec initialisation in
> arm_smmu_register_legacy_master() as it is dereferenced later. Without
> this there is a NULL-pointer dereference panic during boot on some hosts.
>
> Signed-off-by: Artem Savkov <asavkov@redhat.com>
> ---
> drivers/iommu/arm-smmu.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/iommu/arm-smmu.c b/drivers/iommu/arm-smmu.c
> index b97188a..95f1c86 100644
> --- a/drivers/iommu/arm-smmu.c
> +++ b/drivers/iommu/arm-smmu.c
> @@ -1519,6 +1519,7 @@ static int arm_smmu_add_device(struct device *dev)
>
> if (using_legacy_binding) {
> ret = arm_smmu_register_legacy_master(dev, &smmu);
> + fwspec = dev->iommu_fwspec;
> if (ret)
> goto out_free;
> } else if (fwspec && fwspec->ops == &arm_smmu_ops) {
Damn, you're completely right! Robin and I bashed our heads against this for
a while and couldn't remember why the code was structured like it was, but
that explains it. Can you add a comment saying that
arm_smmu_register_legacy_master will allocate an fwspec if its initially NULL,
please?
Cheers,
Will
WARNING: multiple messages have this Message-ID (diff)
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] iommu/arm-smmu: fix null-pointer dereference in arm_smmu_add_device
Date: Tue, 8 Aug 2017 10:26:14 +0100 [thread overview]
Message-ID: <20170808092614.GB12887@arm.com> (raw)
In-Reply-To: <1502182681-8966-1-git-send-email-asavkov@redhat.com>
Hi Artem,
Thanks for the patch.
On Tue, Aug 08, 2017 at 10:58:01AM +0200, Artem Savkov wrote:
> Commit c54451a "iommu/arm-smmu: Fix the error path in arm_smmu_add_device"
> removed fwspec assignment in legacy_binding path as redundant which is
> wrong. It needs to be updated after fwspec initialisation in
> arm_smmu_register_legacy_master() as it is dereferenced later. Without
> this there is a NULL-pointer dereference panic during boot on some hosts.
>
> Signed-off-by: Artem Savkov <asavkov@redhat.com>
> ---
> drivers/iommu/arm-smmu.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/iommu/arm-smmu.c b/drivers/iommu/arm-smmu.c
> index b97188a..95f1c86 100644
> --- a/drivers/iommu/arm-smmu.c
> +++ b/drivers/iommu/arm-smmu.c
> @@ -1519,6 +1519,7 @@ static int arm_smmu_add_device(struct device *dev)
>
> if (using_legacy_binding) {
> ret = arm_smmu_register_legacy_master(dev, &smmu);
> + fwspec = dev->iommu_fwspec;
> if (ret)
> goto out_free;
> } else if (fwspec && fwspec->ops == &arm_smmu_ops) {
Damn, you're completely right! Robin and I bashed our heads against this for
a while and couldn't remember why the code was structured like it was, but
that explains it. Can you add a comment saying that
arm_smmu_register_legacy_master will allocate an fwspec if its initially NULL,
please?
Cheers,
Will
next prev parent reply other threads:[~2017-08-08 9:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-08 8:58 [PATCH] iommu/arm-smmu: fix null-pointer dereference in arm_smmu_add_device Artem Savkov
2017-08-08 8:58 ` Artem Savkov
2017-08-08 9:26 ` Will Deacon [this message]
2017-08-08 9:26 ` Will Deacon
2017-08-08 10:26 ` [PATCH v2] " Artem Savkov
2017-08-08 10:26 ` Artem Savkov
2017-08-08 10:37 ` Robin Murphy
2017-08-08 10:37 ` Robin Murphy
2017-08-08 11:21 ` Will Deacon
2017-08-08 11:21 ` Will Deacon
[not found] ` <20170808112144.GE13355-5wv7dgnIgG8@public.gmane.org>
2017-08-09 21:41 ` David Daney
2017-08-09 21:41 ` David Daney
2017-08-09 21:41 ` David Daney
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=20170808092614.GB12887@arm.com \
--to=will.deacon@arm.com \
--cc=asavkov@redhat.com \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vivek.gautam@codeaurora.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.