Re: [3.0.y, 3.2.y, 3.4.y] Re: ecryptfs: corrupted files on a disk full event

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, 2012-10-10 at 14:32 -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.
[...]

They all sound worthwhile, and I understand they have already had some
testing on Ubuntu's 3.2-based branch.  Therefore, added to the queue.

Ben.

-- 
Ben Hutchings
Always try to do things in chronological order;
it's less confusing that way.

Attachment: signature.asc
Description: This is a digitally signed message part


[Index of Archives]     [Linux Crypto]     [Device Mapper Crypto]     [LARTC]     [Bugtraq]     [Yosemite Forum]

  Powered by Linux