From: Bjorn Helgaas <bhelgaas@google.com>
To: Wei Yang <weiyang@linux.vnet.ibm.com>
Cc: gwshan@linux.vnet.ibm.com, linux-pci@vger.kernel.org
Subject: Re: [PATCH] pci/iov: return a reference to PF on destroying VF
Date: Tue, 5 May 2015 16:29:05 -0500 [thread overview]
Message-ID: <20150505212905.GB24643@google.com> (raw)
In-Reply-To: <1428655984-26903-1-git-send-email-weiyang@linux.vnet.ibm.com>
On Fri, Apr 10, 2015 at 04:53:04PM +0800, Wei Yang wrote:
> Each VF will get a reference to its PF, while it is not returned back in
> all cases and leave a removed PF's pci_dev un-released.
>
> As commit ac205b7b ("PCI: make sriov work with hotplug remove") indicates,
> when removing devices on a bus, we do it in the reverse order. This means
> we would remove VFs first, then PFs. After doing so, VF's removal is done
> with pci_stop_and_remove_bus_device() instead of virtfn_remove().
> virtfn_remove() returns the reference of its PF, while
> pci_stop_and_remove_bus_device() doesn't.
Please use conventional citation style (12-char SHA1).
ac205b7bb72f appeared in v3.4. Did that commit cause a regression?
Should this patch be marked for stable?
"After doing so, VF removal is done with pci_stop_and_remove_device() ..."
After doing what? After removing the VFs and PFs? After commit
ac205b7bb72f?
Prior to your patch, the VF reference was released in virtfn_remove(),
which is only called via pci_disable_sriov(). This typically happens in
a driver .remove() method. The reference is *not* released if we call
pci_stop_and_remove_bus_device(VF) directly, as we would via the
remove_store() (sysfs "remove" file) or hot unplug paths, e.g.,
pciehp_unconfigure_device().
After your patch, the VF reference is released in pci_destroy_dev(). This
is called from pci_disable_sriov(), so it happens in that path as before.
But pci_destroy_dev() is called from pci_stop_and_remove_bus_device(), so
the reference is now released for all the paths that use
pci_stop_and_remove_bus_device().
What about the other things done in virtfn_remove(), e.g., the sysfs link
removal? Your patch fixes a reference count leak, but don't we still have
a sysfs link leak?
It would be useful to mention a way to cause the leak. I suspect writing
to a VF's sysfs "remove" file is the easiest.
> This patches moves the return of PF's reference to pci_destroy_dev() to
> make sure the PF's pci_dev is released in any case.
>
> Signed-off-by: Wei Yang <weiyang@linux.vnet.ibm.com>
> ---
> drivers/pci/iov.c | 1 -
> drivers/pci/remove.c | 5 +++++
> 2 files changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/pci/iov.c b/drivers/pci/iov.c
> index 4b3a4ea..9b04bde 100644
> --- a/drivers/pci/iov.c
> +++ b/drivers/pci/iov.c
> @@ -167,7 +167,6 @@ static void virtfn_remove(struct pci_dev *dev, int id, int reset)
>
> /* balance pci_get_domain_bus_and_slot() */
> pci_dev_put(virtfn);
> - pci_dev_put(dev);
> }
>
> static int sriov_enable(struct pci_dev *dev, int nr_virtfn)
> diff --git a/drivers/pci/remove.c b/drivers/pci/remove.c
> index 8bd76c9..836ddf6 100644
> --- a/drivers/pci/remove.c
> +++ b/drivers/pci/remove.c
> @@ -41,6 +41,11 @@ static void pci_destroy_dev(struct pci_dev *dev)
> list_del(&dev->bus_list);
> up_write(&pci_bus_sem);
>
> +#ifdef CONFIG_PCI_IOV
> + if (dev->is_virtfn)
> + pci_dev_put(dev->physfn);
> +#endif
> +
> pci_free_resources(dev);
> put_device(&dev->dev);
> }
> --
> 1.7.9.5
>
next prev parent reply other threads:[~2015-05-05 21:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-10 8:53 [PATCH] pci/iov: return a reference to PF on destroying VF Wei Yang
2015-05-05 21:29 ` Bjorn Helgaas [this message]
2015-05-06 6:09 ` Wei Yang
2015-05-06 15:30 ` Bjorn Helgaas
2015-05-07 2:35 ` Wei Yang
2015-05-06 7:25 ` Wei Yang
2015-05-06 15:23 ` Bjorn Helgaas
2015-05-07 2:40 ` Wei Yang
2015-05-08 3:53 ` [PATCH V2] pci/iov: fix resource leak " Wei Yang
2015-05-19 23:00 ` Bjorn Helgaas
2015-05-20 1:34 ` Wei Yang
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=20150505212905.GB24643@google.com \
--to=bhelgaas@google.com \
--cc=gwshan@linux.vnet.ibm.com \
--cc=linux-pci@vger.kernel.org \
--cc=weiyang@linux.vnet.ibm.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).