On Fri, Sep 23, 2016 at 04:05:26PM -0400, Theodore Ts'o wrote: > It is sometimes useful to be able to test the local file system > provided in a restricted execution environment (such as that which is > provided by Docker, for example) where it is not possible to mount and > unmount the file system under test. Ignoring the code changes for the moment - what's the reason/use case for running /kernel/ test suites inside a user container with such restricted access to filesystems and devices? Especially considering test failures can take the kernel down, which will kill /everything/ on the machine, not just the container. This doesn't make a whole lot of sense to me - who is going to use this and what extra test coverage does it bring to the table compared to just running inside a guest VM with full privileges? Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe fstests" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
