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

2017-11-17 Thread Tyler Hicks
On 11/15/2017 06:58 PM, Dmitry Torokhov wrote: > On Wed, Apr 26, 2017 at 11:02 AM, 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

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

2017-11-17 Thread Tyler Hicks
On 11/15/2017 06:58 PM, Dmitry Torokhov wrote: > On Wed, Apr 26, 2017 at 11:02 AM, 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

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

2017-11-15 Thread Dmitry Torokhov
On Wed, Apr 26, 2017 at 11:02 AM, 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

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

2017-11-15 Thread Dmitry Torokhov
On Wed, Apr 26, 2017 at 11:02 AM, 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

[PATCH v2] ecryptfs: sync before truncating lower inode

2017-04-26 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,

[PATCH v2] ecryptfs: sync before truncating lower inode

2017-04-26 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,