On Fri, Feb 27, 2009 at 12:34:31PM -0800, Dave Hansen wrote: > > We have set up sane defaults for how filesystems should > be checkpointed. However, as usual in the VFS, there > are specialized places that will always need an ability > to override these defaults. > > This adds a new 'file_operations' function for > checkpointing a file. I did this under the assumption > that we should have a dirt-simple way to make something > (un)checkpointable that fits in with current code. > > As you can see in the /dev/null patch in a second, all > that we have to do to make something like /dev/null > supported is add a single "generic" f_op entry. Please don't do the fallback to allow checkpointing without file operations. We've never had luck with these fallbacks, and I'm in the process of getting of the last default file operation (llseek, which has a very bad default) currently. Incidentally that should also allow you to get rid of the per-fs flag by just checking for the presence of the operation to check if checkpointing is allowed. Also the double-use of the op seem not very nice to me. Is there any real life use case were you would have the operation on a file but sometimes not allow checkpoiting? _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/containers
