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 Mon, Nov 12, 2012 at 05:56:07PM -0200, Herton Ronaldo Krzesinski wrote:
> 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()
> 
> What about also picking the following two for stables?
> 
> 069ddcda37b2cf5bb4b6031a944c0e9359213262
> eCryptfs: Copy up POSIX ACL and read-only flags from lower mount
> 
> 5f5b331d5c21228a6519dcb793fc1629646c51a6
> eCryptfs: check for eCryptfs cipher support at mount

Both now applied to the 3.0 and 3.4 stable trees, 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


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

  Powered by Linux