diff options
author | 2014-10-06 16:40:13 -0700 | |
---|---|---|
committer | 2014-10-07 23:05:07 -0700 | |
commit | 62d3ab49b8a5438d11a11605ea1a6d2fe0118f32 (patch) | |
tree | 8a912af6a32f35c460213f037fa52df70e877283 /tools/perf/util/scripting-engines/trace-event-python.c | |
parent | iser-target: Disable TX completion interrupt coalescing (diff) | |
download | wireguard-linux-62d3ab49b8a5438d11a11605ea1a6d2fe0118f32.tar.xz wireguard-linux-62d3ab49b8a5438d11a11605ea1a6d2fe0118f32.zip |
target/file: fix inclusive vfs_fsync_range() end
Both of the file target's calls to vfs_fsync_range() got the end offset
off by one. The range is inclusive, not exclusive. It would sync a bit
more data than was required.
The sync path already tested the length of the range and fell back to
LLONG_MAX so I copied that pattern in the rw path.
This is untested. I found the errors by inspection while following other
code.
Signed-off-by: Zach Brown <zab@zabbo.net>
Signed-off-by: Nicholas Bellinger <nab@linux-iscsi.org>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions