Re: [PATCH] CHROMIUM: ecryptfs: sync before truncating lower inode

2017-04-26 Thread Andrey Pronin
On Fri, Apr 21, 2017 at 04:52:13PM -0700, Andrey Pronin wrote: > On Thu, Apr 20, 2017 at 06:27:52PM -0500, Tyler Hicks wrote: > > On 04/18/2017 06:36 PM, Andrey Pronin wrote: > > > If the updated ecryptfs header data is not written to disk before > > > the lower file is truncated, a crash may leave

Re: [PATCH] CHROMIUM: ecryptfs: sync before truncating lower inode

2017-04-21 Thread Andrey Pronin
On Thu, Apr 20, 2017 at 06:27:52PM -0500, Tyler Hicks wrote: > On 04/18/2017 06:36 PM, Andrey Pronin wrote: > > If the updated ecryptfs header data is not written to disk before > > the lower file is truncated, a crash may leave the filesystem > > in the state when the lower file truncation is jour

Re: [PATCH] CHROMIUM: ecryptfs: sync before truncating lower inode

2017-04-20 Thread Tyler Hicks
On 04/18/2017 06:36 PM, Andrey Pronin wrote: > If the updated ecryptfs header data is not written to disk before > the lower file is truncated, a crash may leave the filesystem > in the state when the lower file truncation is journaled, while > the changes to the ecryptfs header are lost (if the un

[PATCH] CHROMIUM: ecryptfs: sync before truncating lower inode

2017-04-18 Thread Andrey Pronin
If the updated ecryptfs header data is not written to disk before the lower file is truncated, a crash may leave the filesystem in the state when the lower file truncation is journaled, while the changes to the ecryptfs header are lost (if the underlying filesystem is ext4 in data=ordered mode, for