> I'm afraid that's insufficient. What it would need to do is to is > flush everything (to make sure what's on disk matches what's in > memory), but also read back the filesystem on resume to verify that > nothing else modified it (i.e. making sure what's on disk still matches > what's in memory). For most file systems it is sufficient to check the superblock related information. So we'd need an fs->ops->validate_media() or somesuch but it wouldn't be that horrific or need to do much I/O in most cases. You could defeat that by being really stupid, but the purpose of the check isn't a stupidity filter but to stop accidents happening in normal use. > Another way of putting it is that the kernel needs to umount/mount > around suspend in a way that's transparent to users of the filesystem. No. The kernel needs to push stuff to media on suspend (which is good manners anyway), and validate on resume. if the validate fails you mark the media as changed and the block layer will already see to it that everything gets aborted as it already does with a truely removable device. In fact if you did this by media serial numbers and idents you don't even need the fs hook, although it would certainly be safer that way. Alan -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
