diff options
author | Filipe Manana <fdmanana@suse.com> | 2022-07-04 12:42:04 +0100 |
---|---|---|
committer | David Sterba <dsterba@suse.com> | 2022-07-25 17:45:40 +0200 |
commit | ac5e666951507ceb1da2ed85c4f5c7bb88bec06e (patch) | |
tree | 75ee947458c6cb247605b2b9e3561812f6cf28e0 /mm/highmem.c | |
parent | 8bfc9b2cf468c37870b980a16c345c9ba3a2010a (diff) |
btrfs: don't fallback to buffered IO for NOWAIT direct IO writes
Currently, for a direct IO write, if we need to fallback to buffered IO,
either to satisfy the whole write operation or just a part of it, we do
it in the current context even if it's a NOWAIT context. This is not ideal
because we currently don't have support for NOWAIT semantics in the
buffered IO path (we can block for several reasons), so we should instead
return -EAGAIN to the caller, so that it knows it should retry (the whole
operation or what's left of it) in a context where blocking is acceptable.
Signed-off-by: Filipe Manana <fdmanana@suse.com>
Reviewed-by: David Sterba <dsterba@suse.com>
Signed-off-by: David Sterba <dsterba@suse.com>
Diffstat (limited to 'mm/highmem.c')
0 files changed, 0 insertions, 0 deletions