diff options
author | Jan Kara <jack@suse.cz> | 2016-04-01 02:07:22 -0400 |
---|---|---|
committer | Theodore Ts'o <tytso@mit.edu> | 2016-04-01 02:07:22 -0400 |
commit | e84dfbe2bf170c626778079e5b94435b05b8d572 (patch) | |
tree | d00b3abe754efacc314909b85ceede6d922c533c /fs/9p/vfs_super.c | |
parent | daf647d2dd58cec59570d7698a45b98e580f2076 (diff) | |
download | linux-stable-e84dfbe2bf170c626778079e5b94435b05b8d572.tar.gz linux-stable-e84dfbe2bf170c626778079e5b94435b05b8d572.tar.bz2 linux-stable-e84dfbe2bf170c626778079e5b94435b05b8d572.zip |
ext4: retry block allocation for failed DIO and DAX writes
Currently if block allocation for DIO or DAX write fails due to ENOSPC,
we just returned it to userspace. However these ENOSPC errors can be
transient because the transaction freeing blocks has not yet committed.
This demonstrates as failures of generic/102 test when the filesystem is
mounted with 'dax' mount option.
Fix the problem by properly retrying the allocation in case of ENOSPC
error in get blocks functions used for direct IO.
Signed-off-by: Jan Kara <jack@suse.cz>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Tested-by: Ross Zwisler <ross.zwisler@linux.intel.com>
Diffstat (limited to 'fs/9p/vfs_super.c')
0 files changed, 0 insertions, 0 deletions