[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.44L0.1302201021210.1671-100000@iolanthe.rowland.org>
Date: Wed, 20 Feb 2013 10:24:12 -0500 (EST)
From: Alan Stern <stern@...land.harvard.edu>
To: "Eric W. Biederman" <ebiederm@...ssion.com>
cc: Li Fei <fei.li@...el.com>, <pavel@....cz>, <rjw@...k.pl>,
<len.brown@...el.com>, <mingo@...hat.com>, <peterz@...radead.org>,
<akpm@...ux-foundation.org>, <viro@...iv.linux.org.uk>,
<gorcunov@...nvz.org>, <rientjes@...gle.com>,
<linux-kernel@...r.kernel.org>, <linux-pm@...r.kernel.org>,
<chuansheng.liu@...el.com>, <biao.wang@...el.com>
Subject: Re: [PATCH] freezer: configure user space process frozen along with
kernel threads
On Wed, 20 Feb 2013, Eric W. Biederman wrote:
> Why can't the fuse filesystem freeze when there are requests pending?
It _can_ freeze (that is, the fuse daemon can). The problem is that
tasks _using_ the fuse filsystem can't if the daemon doesn't respond.
These tasks are stuck in uninterruptible wait states deep in the
filesystem layer, probably holding important locks. They can't be
frozen until the outstanding requests complete.
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