On Wed 2013-02-20 13:36:19, Eric W. Biederman wrote:
> Alan Stern writes:
>
> > 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
> >> >
On Wed 2013-02-20 05:51:49, Eric W. Biederman wrote:
> Li Fei writes:
>
> > There is well known issue that freezing will fail in case that fuse
> > daemon is frozen firstly with some requests not handled, as the fuse
> > usage task is waiting for the response from fuse daemon and can't be
> > fro
On Wed, 20 Feb 2013, Eric W. Biederman wrote:
> > Oh, okay. But it's no different from any other filesystem in that
> > respect. Processes generally can't be frozen while they are waiting
> > for filesystem I/O to complete. In many cases they can't receive
> > signals either (they are in an un
Alan Stern writes:
> 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
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.
>
> Which is what I mean
Alan Stern writes:
> 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.
Which is
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 uninterruptib
Li Fei writes:
> There is well known issue that freezing will fail in case that fuse
> daemon is frozen firstly with some requests not handled, as the fuse
> usage task is waiting for the response from fuse daemon and can't be
> frozen. To solve the issue as above, make fuse daemon frozen after
>
nux-foundation.org; v...@zeniv.linux.org.uk;
> ebied...@xmission.com; rient...@google.com; linux-kernel@vger.kernel.org;
> linux...@vger.kernel.org; Liu, Chuansheng; Wang, Biao
> Subject: Re: [PATCH] freezer: configure user space process frozen along with
> kernel threads
>
> On Wed, Feb 20,
On Wed, Feb 20, 2013 at 10:15:25AM +0800, Li Fei wrote:
>
> +#ifdef CONFIG_FREEZER
> +
> +static ssize_t freeze_late_read(struct file *file, char __user *buf,
> + size_t count, loff_t *ppos)
> +{
> + struct task_struct *task = get_proc_task(file->f_path.den
There is well known issue that freezing will fail in case that fuse
daemon is frozen firstly with some requests not handled, as the fuse
usage task is waiting for the response from fuse daemon and can't be
frozen. To solve the issue as above, make fuse daemon frozen after
all user space processes
11 matches
Mail list logo
