[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.44L0.1312241653360.337-100000@netrider.rowland.org>
Date: Tue, 24 Dec 2013 16:55:46 -0500 (EST)
From: Alan Stern <stern@...land.harvard.edu>
To: Tejun Heo <tj@...nel.org>
cc: Linus Torvalds <torvalds@...ux-foundation.org>,
<linux-kernel@...r.kernel.org>, <linux-ide@...r.kernel.org>,
"Rafael J. Wysocki" <rjw@...ysocki.net>, <linux-pm@...r.kernel.org>
Subject: Re: [GIT PULL] libata fixes for v3.13-rc5
On Tue, 24 Dec 2013, Tejun Heo wrote:
> Hello, Linus.
>
> libata fixes for v3.13-rc5. There's one interseting commit - "libata,
> freezer: avoid block device removal while system is frozen". It's an
> ugly hack working around a deadlock condition between driver core
> resume and block layer device removal paths through freezer which was
> made more reproducible by writeback being converted to workqueue some
> releases ago. The bug has nothing to do with libata but it's just an
> workaround which is easy to backport. After discussion, Rafael and I
> seem to agree that we don't really need kernel freezables - both
> kthread and workqueue. There are few specific workqueues which
> constitute PM operations and require freezing, which will be converted
> to use workqueue_set_max_active() instead. All other kernel freezer
> uses are planned to be removed, followed by the removal of kthread and
> workqueue freezer support, hopefully.
Wait a minute. I don't recall anybody mentioning this earlier. What
about khubd? There isn't any plan to remove _it_.
Alan Stern
--
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