[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d120d5000703150622o43763828h5e01f313a3194f39@mail.gmail.com>
Date: Thu, 15 Mar 2007 09:22:25 -0400
From: "Dmitry Torokhov" <dmitry.torokhov@...il.com>
To: "Oliver Neukum" <oneukum@...e.de>
Cc: "Hugh Dickins" <hugh@...itas.com>,
"Cornelia Huck" <cornelia.huck@...ibm.com>,
"Alan Stern" <stern@...land.harvard.edu>,
"Linus Torvalds" <torvalds@...ux-foundation.org>,
"Maneesh Soni" <maneesh@...ibm.com>, gregkh@...e.de,
"Richard Purdie" <rpurdie@...ys.net>,
"James Bottomley" <James.Bottomley@...eleye.com>,
"Kernel development list" <linux-kernel@...r.kernel.org>
Subject: Re: 2.6.21-rc suspend regression: sysfs deadlock
On 3/15/07, Oliver Neukum <oneukum@...e.de> wrote:
> Am Donnerstag, 15. März 2007 13:31 schrieb Hugh Dickins:
> > Quite apart from this mysterious "other task", I don't understand
> > "access" either.
> >
> > Perhaps "defer" would best capture the idea of another-task and
> > maybe-delay? sysfs_defer_work(), struct sysfs_deferred_work?
>
> But we do not wish to defer or delay anything.
> How about: sysfs_action_from_neutral_context
>
How about sysfs_schedule_work? That is what it does - schedules a work
on a sysfs object and everyone here knows what schedule_work() does.
--
Dmitry
-
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