From: Alex Williamson <alex.williamson@redhat.com>
To: Eric Auger <eric.auger@redhat.com>
Cc: eric.auger.pro@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] vfio: fix noiommu vfio_iommu_group_get reference count
Date: Wed, 30 Aug 2017 15:23:31 -0600 [thread overview]
Message-ID: <20170830152331.7cf8c30d@w520.home> (raw)
In-Reply-To: <1502457366-3562-1-git-send-email-eric.auger@redhat.com>
On Fri, 11 Aug 2017 15:16:06 +0200
Eric Auger <eric.auger@redhat.com> wrote:
> In vfio_iommu_group_get() we want to increase the reference
> count of the iommu group.
>
> In noiommu case, the group does not exist and is allocated.
> iommu_group_add_device() increases the group ref count. However we
> then call iommu_group_put() which decrements it.
>
> This leads to a "refcount_t: underflow WARN_ON".
>
> Only decrement the ref count in case of iommu_group_add_device
> failure.
>
> Signed-off-by: Eric Auger <eric.auger@redhat.com>
>
> ---
>
> v1 -> v2:
> put the group in case iommu_group_add_device failed
> ---
> drivers/vfio/vfio.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
Applied to next branch for v4.14. Thanks,
Alex
> diff --git a/drivers/vfio/vfio.c b/drivers/vfio/vfio.c
> index 330d505..4ee4f36 100644
> --- a/drivers/vfio/vfio.c
> +++ b/drivers/vfio/vfio.c
> @@ -138,9 +138,10 @@ struct iommu_group *vfio_iommu_group_get(struct device *dev)
> iommu_group_set_name(group, "vfio-noiommu");
> iommu_group_set_iommudata(group, &noiommu, NULL);
> ret = iommu_group_add_device(group, dev);
> - iommu_group_put(group);
> - if (ret)
> + if (ret) {
> + iommu_group_put(group);
> return NULL;
> + }
>
> /*
> * Where to taint? At this point we've added an IOMMU group for a
prev parent reply other threads:[~2017-08-30 21:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-11 13:16 Eric Auger
2017-08-30 21:23 ` Alex Williamson [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=20170830152331.7cf8c30d@w520.home \
--to=alex.williamson@redhat.com \
--cc=eric.auger.pro@gmail.com \
--cc=eric.auger@redhat.com \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®