diff options
| author | Jan Kara <jack@suse.cz> | 2016-05-11 12:58:49 +0300 |
|---|---|---|
| committer | Vishal Verma <vishal.l.verma@intel.com> | 2016-05-17 09:44:07 +0300 |
| commit | 86b0624e42d03a424e9571b8591d191c436f9af1 (patch) | |
| tree | a00a6ccf33d6f1880ce18f455d8259dc3dc1a326 /fs/dax.c | |
| parent | 9b6cd5f76d60b563d75e55e432e03ed134761432 (diff) | |
| download | linux-86b0624e42d03a424e9571b8591d191c436f9af1.tar.xz | |
ext2: Avoid DAX zeroing to corrupt data
Currently ext2 zeroes any data blocks allocated for DAX inode however it
still returns them as BH_New. Thus DAX code zeroes them again in
dax_insert_mapping() which can possibly overwrite the data that has been
already stored to those blocks by a racing dax_io(). Avoid marking
pre-zeroed buffers as new.
Reviewed-by: Ross Zwisler <ross.zwisler@linux.intel.com>
Signed-off-by: Jan Kara <jack@suse.cz>
Signed-off-by: Vishal Verma <vishal.l.verma@intel.com>
Diffstat (limited to 'fs/dax.c')
0 files changed, 0 insertions, 0 deletions