From: Alex Williamson <alex.williamson@redhat.com>
To: Shuah Khan <shuahkhan@gmail.com>
Cc: Betty Dall <betty.dall@hp.com>,
bhelgaas@google.com, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org, wangyijing@huawei.com,
jiang.liu@huawei.com
Subject: Re: [PATCH] PCI AER: pci_get_domain_bus_and_slot() call missing required pci_dev_put()
Date: Mon, 03 Dec 2012 12:48:04 -0700 [thread overview]
Message-ID: <1354564084.1809.390.camel@bling.home> (raw)
In-Reply-To: <CAKocOOOudEzMx0Zs9CB2zmtCkPHVkx1TCbWeK2+uoV5cb=eiGg@mail.gmail.com>
On Mon, 2012-12-03 at 10:40 -0700, Shuah Khan wrote:
> On Mon, Dec 3, 2012 at 9:37 AM, Betty Dall <betty.dall@hp.com> wrote:
> > The function aer_recover_queue() makes a call to pci_get_domain_bus_and_slot().
> > That function is documented to require that the caller decrement the
> > reference count by calling pci_dev_put(). This patch adds the missing
> > call to pci_dev_put().
> >
> > Signed-off-by: Betty Dall <betty.dall@hp.com>
> > ---
> > drivers/pci/pcie/aer/aerdrv_core.c | 1 +
> > 1 files changed, 1 insertions(+), 0 deletions(-)
> >
> > diff --git a/drivers/pci/pcie/aer/aerdrv_core.c b/drivers/pci/pcie/aer/aerdrv_core.c
> > index af4e31c..43caf53 100644
> > --- a/drivers/pci/pcie/aer/aerdrv_core.c
> > +++ b/drivers/pci/pcie/aer/aerdrv_core.c
> > @@ -616,6 +616,7 @@ static void aer_recover_work_func(struct work_struct *work)
> > continue;
> > }
> > do_recovery(pdev, entry.severity);
> > + pci_dev_put(pdev);
>
> Are you sure pci_get_domain_bus_and_slot() does indeed increment the
> reference count? I see that in the comments right above the
> definition.
>
> pci_dev_get() does that for sure. I see a call trace of
>
> pci_dev_get() -> get_device() -> kobj_to_dev(kobject_get(&dev->kobj) etc.
>
> and kref_get() finally incrementing the
>
> static inline void kref_get(struct kref *kref)
> {
> WARN_ON(!atomic_read(&kref->refcount));
> atomic_inc(&kref->refcount);
> }
>
> However, I could not find any evidence that
> pci_get_domain_bus_and_slot() does that. I see
> pci_get_domain_bus_and_slot() calling pci_domain_nr() and there are
> several architecture specific defines for pci_domain_nr(). It is not
> clear to me where does refcount get incremented from
> pci_get_domain_bus_and_slot() is called.
>
> What am I missing?
Trace back the for_each_pci_dev()
for_each_pci_dev
-> pci_get_device
-> pci_get_subsys
-> pci_get_dev_by_id
-> bus_find_device
-> get_device()
The real question is how many places do we call for_each_pci_dev()
without a put. It seems like pci_get_domain_bus_and_slot() doesn't even
get it right since it should include a put of the non-matched devices.
Thanks,
Alex
next prev parent reply other threads:[~2012-12-03 19:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-03 16:37 [PATCH] PCI AER: pci_get_domain_bus_and_slot() call missing required pci_dev_put() Betty Dall
2012-12-03 17:40 ` Shuah Khan
2012-12-03 19:48 ` Alex Williamson [this message]
2012-12-03 20:00 ` Alex Williamson
2012-12-03 20:59 ` Shuah Khan
2013-01-07 18:46 ` Bjorn Helgaas
2012-12-03 20:01 ` Shuah Khan
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=1354564084.1809.390.camel@bling.home \
--to=alex.williamson@redhat.com \
--cc=betty.dall@hp.com \
--cc=bhelgaas@google.com \
--cc=jiang.liu@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=shuahkhan@gmail.com \
--cc=wangyijing@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