On Wed, Oct 10, 2012 at 02:32:03PM -0700, Jonathan Nieder wrote: > Hi Ben and Greg, > > Please consider > > 8bc2d3cf6129 eCryptfs: Unlink lower inode when ecryptfs_create() fails > e3ccaa976120 eCryptfs: Initialize empty lower files when opening them > 821f7494a776 eCryptfs: Revert to a writethrough cache model > 7149f2558d5b eCryptfs: Write out all dirty pages just before releasing the > lower file > 64e6651dcc10 eCryptfs: Call lower ->flush() from ecryptfs_flush() > > for application to the 3.0.y, 3.2.y, and 3.4.y trees. (These fixes were > all applied to mainline during the 3.6 cycle.) > > The patches apply cleanly to 3.2.y. The backport to 3.0.y would take more > work since it lacks, for example, b59db43ad443 (eCryptfs: Prevent file > create race condition, 2011-11-21). > > Patches 1-4 improve error handling and recovery. The fifth ensures > flushes get propagated to the underlying filesystem, which would be > important to avoid data loss from power loss or crashes. Applied to the 3.4 tree, they didn't work on 3.0. If you have backports for 3.0, that would be great to have. thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe ecryptfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
