diff options
author | 2022-03-24 23:13:26 +0100 | |
---|---|---|
committer | 2022-03-24 23:40:43 +0100 | |
commit | 3bde4c48586074202044456285a97ccdf9048988 (patch) | |
tree | 473c22c835a05f8177016a401c82749b041f37c4 /tools/perf/util/scripting-engines/trace-event-python.c | |
parent | gfs2: Remove dead code in gfs2_file_read_iter (diff) | |
download | wireguard-linux-3bde4c48586074202044456285a97ccdf9048988.tar.xz wireguard-linux-3bde4c48586074202044456285a97ccdf9048988.zip |
gfs2: Make sure not to return short direct writes
When direct writes fail with -ENOTBLK because we're writing into a
hole (gfs2_iomap_begin()) or because of a page invalidation failure
(iomap_dio_rw()), we're falling back to buffered writes. In that case,
when we lose the inode glock in gfs2_file_buffered_write(), we want to
re-acquire it instead of returning a short write.
Signed-off-by: Andreas Gruenbacher <agruenba@redhat.com>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions