diff options
| author | Al Viro <viro@zeniv.linux.org.uk> | 2016-09-06 04:42:32 +0300 |
|---|---|---|
| committer | Al Viro <viro@zeniv.linux.org.uk> | 2016-12-10 06:41:47 +0300 |
| commit | c0cf3ef5e0f47e385920450b245d22bead93e7ad (patch) | |
| tree | 81db472b3d4c969ba0e3c9423ddad79ff793cc69 /fs/locks.c | |
| parent | e5517c2a5a49ed5e99047008629f1cd60246ea0e (diff) | |
| download | linux-c0cf3ef5e0f47e385920450b245d22bead93e7ad.tar.xz | |
nfs_write_end(): fix handling of short copies
What matters when deciding if we should make a page uptodate is
not how much we _wanted_ to copy, but how much we actually have
copied. As it is, on architectures that do not zero tail on
short copy we can leave uninitialized data in page marked uptodate.
Cc: stable@vger.kernel.org
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Diffstat (limited to 'fs/locks.c')
0 files changed, 0 insertions, 0 deletions