[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200801062005.12097.rjw@sisk.pl>
Date: Sun, 6 Jan 2008 20:05:11 +0100
From: "Rafael J. Wysocki" <rjw@...k.pl>
To: Alan Stern <stern@...land.harvard.edu>
Cc: Greg KH <gregkh@...e.de>,
Andrew Morton <akpm@...ux-foundation.org>,
Len Brown <lenb@...nel.org>, Ingo Molnar <mingo@...e.hu>,
ACPI Devel Maling List <linux-acpi@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
pm list <linux-pm@...ts.linux-foundation.org>
Subject: Re: [PATCH] PM: Acquire device locks on suspend
On Sunday, 6 of January 2008, Alan Stern wrote:
> On Sun, 6 Jan 2008, Rafael J. Wysocki wrote:
>
> > > If you can figure out a way to disable the warning in device_del() for
> > > just the one device being unregistered by
> > > device_pm_destroy_suspended(),
> >
> > Something like this, perhaps:
> >
> > @@ -905,6 +915,18 @@ void device_del(struct device * dev)
> > struct device * parent = dev->parent;
> > struct class_interface *class_intf;
> >
> > + if (down_trylock(&dev->sem)) {
> > + if (pm_sleep_lock()) {
> > + dev_warn(dev, "Illegal %s during suspend\n",
> > + __FUNCTION__);
> > + dump_stack();
> > + } else {
> > + pm_sleep_unlock();
> > + }
> > + } else {
> > + up(&dev->sem);
> > + }
> > +
> > if (parent)
> > klist_del(&dev->knode_parent);
> > if (MAJOR(dev->devt))
>
> Bizarre, but it should work.
OK
Still, shouldn't we fail the removal of the device apart from giving the
warning?
> Be sure to include plenty of explanatory comments
I will.
I think that code can be moved to its own function in
drivers/base/power/main.c, btw.
> -- otherwise nobody will be able to figure it out! :-)
Well, I guess so. :-)
Thanks,
Rafael
--
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