From: Lu Baolu <baolu.lu@linux.intel.com>
To: Yang Yingliang <yangyingliang@huawei.com>,
iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iommu: fix return error code in iommu_probe_device()
Date: Tue, 17 Nov 2020 17:40:25 +0800 [thread overview]
Message-ID: <835ab066-b6b8-a211-4941-c01781031de8@linux.intel.com> (raw)
In-Reply-To: <20201117025238.3425422-1-yangyingliang@huawei.com>
Hi Yingliang,
On 2020/11/17 10:52, Yang Yingliang wrote:
> If iommu_group_get() failed, it need return error code
> in iommu_probe_device().
>
> Fixes: cf193888bfbd ("iommu: Move new probe_device path...")
> Reported-by: Hulk Robot <hulkci@huawei.com>
> Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
> ---
> drivers/iommu/iommu.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/iommu/iommu.c b/drivers/iommu/iommu.c
> index b53446bb8c6b..6f4a32df90f6 100644
> --- a/drivers/iommu/iommu.c
> +++ b/drivers/iommu/iommu.c
> @@ -253,8 +253,10 @@ int iommu_probe_device(struct device *dev)
> goto err_out;
>
> group = iommu_group_get(dev);
> - if (!group)
> + if (!group) {
> + ret = -ENODEV;
Can you please explain why you use -ENODEV here?
Best regards,
baolu
> goto err_release;
> + }
>
> /*
> * Try to allocate a default domain - needs support from the
>
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2020-11-17 9:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-17 2:52 [PATCH] iommu: fix return error code in iommu_probe_device() Yang Yingliang
2020-11-17 9:40 ` Lu Baolu [this message]
2020-11-17 11:11 ` Yang Yingliang
2020-11-17 22:41 ` Will Deacon
2020-11-25 1:54 ` Yang Yingliang
2020-11-25 11:35 ` Will Deacon
2020-11-26 2:29 ` Yang Yingliang
2020-11-26 8:59 ` Will Deacon
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=835ab066-b6b8-a211-4941-c01781031de8@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yangyingliang@huawei.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;
as well as URLs for NNTP newsgroup(s).