From: Alex Chiang <achiang@hp.com>
To: Greg KH <gregkh@suse.de>
Cc: Matthew Wilcox <matthew@wil.cx>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: refcount leak in pci_get_device()?
Date: Thu, 21 Aug 2008 16:14:38 -0600 [thread overview]
Message-ID: <20080821221438.GC20014@ldl.fc.hp.com> (raw)
In-Reply-To: <20080821204758.GB31543@suse.de>
* Greg KH <gregkh@suse.de>:
> On Thu, Aug 21, 2008 at 02:25:04PM -0600, Matthew Wilcox wrote:
> > On Thu, Aug 21, 2008 at 02:19:18PM -0600, Alex Chiang wrote:
> > > #define for_each_pci_dev(d) while ((d = pci_get_device(PCI_ANY_ID, PCI_ANY_ID, d)) != NULL)
> > >
> > > That eventually calls pci_get_dev_by_id(), which increases the
> > > refcount on the device, but never decrements it.
> > >
> > > Looks like that change in behavior happened here:
> > >
> > > PCI: clean up search.c a lot
> > > 95247b57ed844511a212265b45cf9a919753aea1
> > >
> > > pci_get_device() used to decrement the refcount, but no longer
> > > does.
> > >
> > > Thanks to Matthew Wilcox for helping me get this far...
> > >
> > > Like I said, I'm still trying to track down my particular issue,
> > > but I'd like to get your opinion on this.
> >
> > In particular, I'd like to know whether this should be fixed by
> > pci_get_dev_by_id() decrementing the refcount of from/dev_start,
> > pci_get_subsys() decrementing 'from', or by bus_find_device()
> > decrementing 'start'. It looks like bus_find_device() is the place
> > where this should logically happen, but the kerneldoc doesn't document
> > the intended behaviour.
>
> Ah, no the driver core isn't supposed to do this, it's something the pci
> functions do out of "niceness" as that's how we can use them in an
> iterator properly.
>
> Does the following (untested) patch fix the issue for you all?
Perfect, yes.
I applied it, and observed the refcount on the device I was using
to debug this problem.
I was able to modprobe acpiphp successfully, and echo 0 into the
device's 'power' file.
I then watched the rest of the hotplug core do its thing,
decrementing the refcount properly along the way, and at the end,
we did call pci_release_dev(), as I originally expected to. :)
Just to verify, I toggled the device's power a few times (echoing
a 1 and then a 0, etc.) and watched the refcounts. After each
offline, we properly called pci_release_dev().
Thanks for fixing this. It fixes a pretty bad leak in the hotplug
core (we were leaking an entire struct pci_dev * # of functions
for each offlined card, the first time around; subsequent
onlines/offlines were ok).
Tested-by: Alex Chiang <achiang@hp.com>
/ac
>
> thanks,
>
> greg k-h
>
> --------------
> Subject: PCI: fix reference leak in pci_get_dev_by_id()
>
> From: Greg Kroah-Hartman <gregkh@suse.de>
>
> Alex Chiang and Matthew Wilcox pointed out that pci_get_dev_by_id() does
> not properly decrement the reference on the from pointer if it is
> present, like the documentation for the function states it will.
>
> Cc: Matthew Wilcox <matthew@wil.cx>
> Cc: Alex Chiang <achiang@hp.com>
> Cc: stable <stable@kernel.org>
> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
>
>
> diff --git a/drivers/pci/search.c b/drivers/pci/search.c
> index 217814f..3b3b5f1 100644
> --- a/drivers/pci/search.c
> +++ b/drivers/pci/search.c
> @@ -280,6 +280,8 @@ static struct pci_dev *pci_get_dev_by_id(const struct pci_device_id *id,
> match_pci_dev_by_id);
> if (dev)
> pdev = to_pci_dev(dev);
> + if (from)
> + pci_dev_put(from);
> return pdev;
> }
>
>
next prev parent reply other threads:[~2008-08-21 22:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-21 20:19 refcount leak in pci_get_device()? Alex Chiang
2008-08-21 20:25 ` Matthew Wilcox
2008-08-21 20:47 ` Greg KH
2008-08-21 22:14 ` Alex Chiang [this message]
2008-08-30 4:23 ` Zhao, Yu
2008-08-30 5:37 ` Greg KH
2008-08-30 6:20 ` Zhao, Yu
2008-08-31 3:14 ` problems in fakephp (was RE: refcount leak in pci_get_device()?) Zhao, Yu
2008-09-01 18:40 ` [PATCH] PCI Hotplug: fakephp: fix deadlock... again Alex Chiang
2008-09-02 0:10 ` Matthew Wilcox
2008-09-02 0:19 ` Alex Chiang
2008-09-09 4:12 ` Jesse Barnes
2008-09-09 4:27 ` Matthew Wilcox
2008-09-09 5:32 ` Andrew Patterson
2008-09-04 15:03 ` Zhao, Yu
2008-08-21 22:23 ` refcount leak in pci_get_device()? Jesse Barnes
2008-08-22 1:04 ` Henrique de Moraes Holschuh
2008-08-22 1:09 ` Henrique de Moraes Holschuh
2008-08-21 20:40 ` Greg KH
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=20080821221438.GC20014@ldl.fc.hp.com \
--to=achiang@hp.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=matthew@wil.cx \
/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