On Sun, Dec 22, 2013 at 12:33:18AM +0100, Pavel Machek wrote: > Hi! > > > > > > > I disagree - given the problem it is resolving leads to silent > > > > > > filesystem corruption, this patch should be considered somewhat of a > > > > > > priority to push... > > > > > > > > > > Umm. Ok, I forgot what it does, really. > > > > > > > > It ensures that the filesystem is in an quiescent state both in > > > > memory and on disk, and it cannot be modified in memory or on disk > > > > whilst the suspend image is being generated, or by log recovery > > > > after a resume before the suspended image has been restored. > > > > > > If someone attempts to run log recovery before resume, that's a bug > > > and yes, it will corrupt filesystems. (Including ext3). Don't do that. > > > > Freezing the filesystem prevents that accidental mount of the > > filesystem from being an issue. It fixes a bug that: > > Can you elaborate on that? > > If you do read-write mount of that filesystem, surely filesystem > metadata will differ from what the filesystem expects. You'll still > get data corruption AFAICT. Only if you modify stuff. That's not what we are protecting against, it's avoiding the automatic journal replay that you can't avoid if you accidentally mount the filesystem. > Read-only mount... maybe that will get slightly better -- there'll be > no journal to play back. But what happens to superblock information > such as "last mount time"? Mount counts? If metadata is being modified on a read only mount outside of journal replay, then the filesystem needs fixing. > > > > Documentation/power/swsusp.txt: > > > > > > * BIG FAT WARNING > > > ********************************************************* > > > * > > > * If you touch anything on disk between suspend and resume... > > > * ...kiss your data goodbye. > > > > Makes this a whole lot less dangerous. > > Do you claim that it is now safe to mount (rw) and access filesystem > between suspend and resume? No, I didn't claim that. "less dangerous" is still dangerous, just less so than it was before. Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
