On 10/14/2009 10:12 AM, Christoph Hellwig wrote: > It looks like ecryptfs calls vmtruncate directly on the lower filesystem, > which is quite wrong. Vmtruncate is only a helper for the filesystem, > and while most filesystems end up calling vmtruncate from their > ->setattr implementation if ATTR_SIZE is set there are many that require > additional work. I think ecryptfs needs to got through notify_change() > / ->setattr if it wants truncate to work reliably and without silent > corruption or leaking blocks on a variety of filesystems. Thanks Christoph! I agree and will write up a patch shortly. I also opened a bug to track the progress: https://bugs.launchpad.net/ecryptfs/+bug/451368 Tyler -- 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
