From: Gu Zheng <guz.fnst@cn.fujitsu.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] PCI: Fix racing for pci device removing via sysfs
Date: Mon, 29 Apr 2013 18:04:56 +0800 [thread overview]
Message-ID: <517E45C8.4060407@cn.fujitsu.com> (raw)
In-Reply-To: <CAE9FiQWv-bN2XzHiQ0WU+Y678zcqs_Owua6vXXijdMO6=0OWpg@mail.gmail.com>
Hi Yinghai,
On 04/27/2013 05:01 AM, Yinghai Lu wrote:
> On Fri, Apr 26, 2013 at 1:53 PM, Bjorn Helgaas <bhelgaas@google.com> wrote:
>
>>
>> You can't be serious. This is a disgusting mess. Checking a list
>> pointer for LIST_POISON1? As far as I'm concerned, this is a waste of
>> my time.
>
> Well, then need to hold the bus ref, and check bus->devices list instead.
@@ -341,6 +352,7 @@ remove_store(struct device *dev, struct
{
int err;
unsigned long val;
+ struct pci_dev *pdev;
if (strict_strtoul(buf, 0, &val) < 0)
return -EINVAL;
@@ -351,9 +363,14 @@ remove_store(struct device *dev, struct
/* An attribute cannot be unregistered by one of its own methods,
* so we have to use this roundabout approach.
*/
+ pdev = pci_dev_get(to_pci_dev(dev));
There is no need to increase pci_dev's ref here, because we'll increase it
in sysfs_schedule_callback.
+ get_device(&pdev->bus->dev);
So the pci_bus' ref management is still needed.
err = device_schedule_callback(dev, remove_callback);
- if (err)
+ if (err) {
+ put_device(&pdev->bus->dev);
+ pci_dev_put(pdev);
return err;
+ }
return count;
}
next prev parent reply other threads:[~2013-04-29 11:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-26 1:47 [PATCH] PCI: Fix racing for pci device removing via sysfs Yinghai Lu
2013-04-26 16:28 ` Bjorn Helgaas
2013-04-26 20:20 ` Yinghai Lu
2013-04-26 20:53 ` Bjorn Helgaas
2013-04-26 21:01 ` Yinghai Lu
2013-04-29 10:04 ` Gu Zheng [this message]
2013-04-29 15:19 ` Yinghai Lu
2013-04-29 18:15 ` Bjorn Helgaas
2013-04-29 18:21 ` Greg Kroah-Hartman
2013-04-29 21:23 ` Sarah Sharp
2013-04-29 21:32 ` Greg Kroah-Hartman
2013-04-29 22:17 ` Yinghai Lu
2013-04-30 21:29 ` Yinghai Lu
2013-05-08 23:43 ` Bjorn Helgaas
2013-04-30 9:17 ` Gu Zheng
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=517E45C8.4060407@cn.fujitsu.com \
--to=guz.fnst@cn.fujitsu.com \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=yinghai@kernel.org \
/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