[lkml]   [2007]   [Jul]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH] Remove process freezer from suspend to RAM pathway
    > > 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?

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2007-07-03 08:55    [W:0.018 / U:11.432 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site