From: Baolu Lu <baolu.lu@linux.intel.com>
To: Chenyuan Mi <cymi20@fudan.edu.cn>, joro@8bytes.org
Cc: baolu.lu@linux.intel.com, will@kernel.org, robin.murphy@arm.com,
iommu@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iommu: Fix missing check for return value of iommu_group_get()
Date: Thu, 15 Jun 2023 10:31:22 +0800 [thread overview]
Message-ID: <e8304083-931b-f52d-9865-8a79ba96c370@linux.intel.com> (raw)
In-Reply-To: <20230614154308.118783-1-cymi20@fudan.edu.cn>
On 6/14/23 11:43 PM, Chenyuan Mi wrote:
> The iommu_group_get() function may return NULL, which may
> cause null pointer deference, and most other callsites of
> iommu_group_get() do Null check. Add Null check for return
> value of iommu_group_get().
>
> Found by our static analysis tool.
>
> Signed-off-by: Chenyuan Mi <cymi20@fudan.edu.cn>
> ---
> drivers/iommu/iommu.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/iommu/iommu.c b/drivers/iommu/iommu.c
> index f1dcfa3f1a1b..ef3483e75511 100644
> --- a/drivers/iommu/iommu.c
> +++ b/drivers/iommu/iommu.c
> @@ -3217,6 +3217,8 @@ EXPORT_SYMBOL_GPL(iommu_group_release_dma_owner);
> void iommu_device_release_dma_owner(struct device *dev)
> {
> struct iommu_group *group = iommu_group_get(dev);
> + if (!group)
> + return;
This interface should never be used in this way.
Check the comments of this function:
"Release the DMA ownership claimed by iommu_device_claim_dma_owner()."
iommu group has been checked in the claim api.
If any driver misuses this api, a null pointer deference warning is
better than ignoring silently.
>
> mutex_lock(&group->mutex);
> if (group->owner_cnt > 1)
> @@ -3329,6 +3331,8 @@ void iommu_detach_device_pasid(struct iommu_domain *domain, struct device *dev,
> ioasid_t pasid)
> {
> struct iommu_group *group = iommu_group_get(dev);
> + if (!group)
> + return;
Ditto...
>
> mutex_lock(&group->mutex);
> __iommu_remove_group_pasid(group, pasid);
Best regards,
baolu
prev parent reply other threads:[~2023-06-15 2:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-14 15:43 [PATCH] iommu: Fix missing check for return value of iommu_group_get() Chenyuan Mi
2023-06-14 16:29 ` Robin Murphy
2023-06-15 2:31 ` Baolu Lu [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=e8304083-931b-f52d-9865-8a79ba96c370@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=cymi20@fudan.edu.cn \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=will@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox