[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20120502214815.GC27281@kroah.com>
Date: Wed, 2 May 2012 14:48:15 -0700
From: Greg KH <gregkh@...uxfoundation.org>
To: Jiang Liu <jiang.liu@...wei.com>
Cc: Jiang Liu <liuj97@...il.com>, Yinghai Lu <yinghai@...nel.org>,
Kenji Kaneshige <kaneshige.kenji@...fujitsu.com>,
Bjorn Helgaas <bhelgaas@...gle.com>,
Don Dutile <ddutile@...hat.com>,
Keping Chen <chenkeping@...wei.com>,
linux-kernel@...r.kernel.org, linux-pci@...r.kernel.org
Subject: Re: [PATCH v2 04/19] PCI: serialize hotplug operations triggered by
PCI hotplug sysfs interfaces
On Wed, May 02, 2012 at 03:20:15PM +0800, Jiang Liu wrote:
> On 2012-5-2 13:06, Greg KH wrote:
> >On Fri, Apr 27, 2012 at 11:16:45PM +0800, Jiang Liu wrote:
> >>+ /* Avoid deadlock with pci_hp_deregister() */
> >>+ while (!pci_hotplug_try_enter()) {
> >>+ /* Check whether the slot has been deregistered. */
> >>+ if (list_empty(&slot->slot_list)) {
> >>+ retval = -ENODEV;
> >>+ goto exit_put;
> >>+ }
> >>+ msleep(1);
> >>+ }
> >
> >Oh my.
> >
> >Wow.
> >
> >{sigh}
> >
> >ick.
> >
> >My eyes hurt.
> >
> >And your cpu load just went crazy.
> >
> >You can now handle all of the nasty emails from sysadmins asking why
> >their systems look like their load is high for no good reason.
> My bad, should use schedule_timeout_interruptible() instead of
> msleep(1) here to avoid busy waiting.
Um, no, that's not my main point here at all.
My main point is this type of loop is the wrong thing to do in the first
place.
Please redo this whole thing, as explained in my first email in this
thread.
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists