From: Greg KH <gregkh@suse.de>
To: "Zhao, Yu" <yu.zhao@intel.com>
Cc: Alex Chiang <achiang@hp.com>, Matthew Wilcox <matthew@wil.cx>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: refcount leak in pci_get_device()?
Date: Fri, 29 Aug 2008 22:37:55 -0700 [thread overview]
Message-ID: <20080830053755.GA16219@suse.de> (raw)
In-Reply-To: <7A25B56E4BE99C4283EB931CD1A40E110177E488@pdsmsx414.ccr.corp.intel.com>
On Sat, Aug 30, 2008 at 12:23:20PM +0800, Zhao, Yu wrote:
> And the pci_get_dev_by_id() is not safe again the PCI device removal.
> It might fire a warning in bus_find_device() when reference count of
> the knode_bus is decreased to 0 by pci_remove_bus().
Is this something new? Hasn't this always been that way? Why would you
be wanting to call this function anyway?
thanks,
greg k-h
next prev parent reply other threads:[~2008-08-30 5:38 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
2008-08-30 4:23 ` Zhao, Yu
2008-08-30 5:37 ` Greg KH [this message]
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=20080830053755.GA16219@suse.de \
--to=gregkh@suse.de \
--cc=achiang@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=yu.zhao@intel.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