From: "Zhao, Yu" <yu.zhao@intel.com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Yu Zhao <yu.zhao@uniscape.net>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"greg@kroah.com" <greg@kroah.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"stable@kernel.org" <stable@kernel.org>,
Rakib Mullick <rakib.mullick@gmail.com>
Subject: Re: [PATCH] pci: Fixing drivers/pci/search.c compilation warning.
Date: Mon, 27 Oct 2008 11:18:43 +0800 [thread overview]
Message-ID: <49053313.9080706@intel.com> (raw)
In-Reply-To: <20081026183412.GX26094@parisc-linux.org>
Matthew Wilcox wrote:
> On Sun, Oct 26, 2008 at 08:51:25PM +0800, Yu Zhao wrote:
>> This reminds me of other problems of PCI search functions.
>>
>> The 'dev_start' is passed to bus_find_device(), and its 'knode_bus'
>> reference count is decreased by klist_iter_init_node() in that function.
>> The problem is the reference count may be already decrease to 0 because
>> the PCI device 'from' is hot-plugged off (e.g., pci_remove_bus) when the
>> search goes. A warning is fired when klist_iter_init_node() detects the
>> reference count becomes 0.
>>
>> Some code uses pci_find_device() in a way that is not safe with the
>> hotplug, because a device may be destroyed after bus_find_device()
>> returns it and before it's held by pci_dev_get() in the next round.
>> Following is an example from a random grep:
>
> Yes, that's why pci_find_device() is deprecated. But it doesn't also
> need to be buggy ;-)
>
How about pci_get_bus_and_slot()? People would meet the problem with it
anyway.
Thanks,
Yu
next prev parent reply other threads:[~2008-10-27 3:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <b9df5fa10809280816u23ef3021k7eee287a237b72ae@mail.gmail.com>
2008-09-28 16:32 ` [PATCH] pci: Fixing drivers/pci/search.c compilation warning Matthew Wilcox
2008-10-21 1:13 ` Matthew Wilcox
2008-10-21 1:29 ` Jesse Barnes
2008-10-21 17:24 ` Jesse Barnes
2008-10-26 12:51 ` Yu Zhao
2008-10-26 18:34 ` Matthew Wilcox
2008-10-27 3:18 ` Zhao, Yu [this message]
2008-10-27 7:07 ` Matthew Wilcox
2008-10-27 7:13 ` Zhao, Yu
2008-10-27 7:21 ` Matthew Wilcox
2008-10-27 7:34 ` Zhao, Yu
2008-10-27 7:43 ` Zhao, Yu
2008-10-27 7:45 ` Matthew Wilcox
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=49053313.9080706@intel.com \
--to=yu.zhao@intel.com \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=rakib.mullick@gmail.com \
--cc=stable@kernel.org \
--cc=yu.zhao@uniscape.net \
/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