diff options
author | Ross Zwisler <ross.zwisler@linux.intel.com> | 2017-10-12 11:54:08 -0400 |
---|---|---|
committer | Theodore Ts'o <tytso@mit.edu> | 2017-10-12 11:54:08 -0400 |
commit | e9072d859df3e0f2c3ba450f0d1739595c2d5d13 (patch) | |
tree | 8e91f9ce1bd1fdaf439d246e9d8045fd418a61d2 /crypto | |
parent | 559db4c6d784ceedc2a5418ced4d357cb843e221 (diff) | |
download | linux-e9072d859df3e0f2c3ba450f0d1739595c2d5d13.tar.gz |
ext4: prevent data corruption with journaling + DAX
The current code has the potential for data corruption when changing an inode's journaling mode, as that can result in a subsequent unsafe change in S_DAX. I've captured an instance of this data corruption in the following fstest: https://patchwork.kernel.org/patch/9948377/ Prevent this data corruption from happening by disallowing changes to the journaling mode if the '-o dax' mount option was used. This means that for a given filesystem we could have a mix of inodes using either DAX or data journaling, but whatever state the inodes are in will be held for the duration of the mount. Signed-off-by: Ross Zwisler <ross.zwisler@linux.intel.com> Signed-off-by: Theodore Ts'o <tytso@mit.edu> Reviewed-by: Jan Kara <jack@suse.cz> Cc: stable@vger.kernel.org
Diffstat (limited to 'crypto')
0 files changed, 0 insertions, 0 deletions