diff options
| author | Al Viro <viro@zeniv.linux.org.uk> | 2015-04-08 17:00:32 -0400 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2015-04-19 10:10:50 +0200 |
| commit | f3326a5594dbb8faf47fb105740baa936d3445d1 (patch) | |
| tree | 9a0f8b6a82a2f637789d22550e521739661d296d /kernel/task_work.c | |
| parent | 054fa2f11b8458100b7c839a728f0439be863740 (diff) | |
ocfs2: _really_ sync the right range
commit 64b4e2526d1cf6e6a4db6213d6e2b6e6ab59479a upstream.
"ocfs2 syncs the wrong range" had been broken; prior to it the
code was doing the wrong thing in case of O_APPEND, all right,
but _after_ it we were syncing the wrong range in 100% cases.
*ppos, aka iocb->ki_pos is incremented prior to that point,
so we are always doing sync on the area _after_ the one we'd
written to.
Spotted by Joseph Qi <joseph.qi@huawei.com> back in January;
unfortunately, I'd missed his mail back then ;-/
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'kernel/task_work.c')
0 files changed, 0 insertions, 0 deletions