diff options
author | Al Viro <viro@zeniv.linux.org.uk> | 2015-04-08 17:00:32 -0400 |
---|---|---|
committer | Al Viro <viro@zeniv.linux.org.uk> | 2015-04-09 07:18:48 -0400 |
commit | 64b4e2526d1cf6e6a4db6213d6e2b6e6ab59479a (patch) | |
tree | a49bfdd4b0eb85b45ce8fd11ba72f6b0e6145a51 /scripts/recordmcount.pl | |
parent | 9ce5a232b8a941be9e74c055535d81508207a570 (diff) |
ocfs2: _really_ sync the right range
"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 ;-/
Cc: stable@vger.kernel.org
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Diffstat (limited to 'scripts/recordmcount.pl')
0 files changed, 0 insertions, 0 deletions