> > Suspend to RAM on a machine with / on a fuse filesystem turns out to be
> > a screaming nightmare - either the suspend fails because syslog (for
> > instance) can't be frozen, or the machine deadlocks for some other
> > reason I haven't tracked down. We could "fix" fuse, or alternatively we
> > could do what we do for suspend to RAM on other platforms (PPC and APM)
> > and just not use the freezer.
>
> Only if you want to audit all character devices' read() and write()
> methods for races against suspend().
> / on fuse is a bad idea.
What makes / special? Why aren't all fuse filesystems affected?
Suspend isn't trying to do I/O on the root fs, is it?
Miklos
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
