Al Viro 64b4e2526d 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>
2015-04-09 07:18:48 -04:00
..
2014-11-19 13:01:20 -05:00
2013-06-29 12:57:02 +04:00
2011-07-25 14:58:15 -07:00
2015-04-09 07:18:48 -04:00
2008-10-13 13:57:57 -07:00
2014-01-21 16:19:41 -08:00
2008-02-03 17:33:42 +02:00
2011-03-31 11:26:23 -03:00
2012-05-29 23:28:40 -04:00
2015-02-10 14:30:29 -08:00