diff options
| author | Al Viro <viro@zeniv.linux.org.uk> | 2016-09-05 21:42:32 -0400 |
|---|---|---|
| committer | Sasha Levin <alexander.levin@verizon.com> | 2017-01-12 20:56:56 -0500 |
| commit | 576cfe615febe0eccc95f7884ef998d15024b025 (patch) | |
| tree | a02f8d5a56aa19dc0d71fddb72183a602792d2a6 /samples | |
| parent | 77f3c11c13ddf7aa5b63b1f8b2e238d93cc6ecaf (diff) | |
nfs_write_end(): fix handling of short copies
[ Upstream commit c0cf3ef5e0f47e385920450b245d22bead93e7ad ]
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>
Signed-off-by: Sasha Levin <alexander.levin@verizon.com>
Diffstat (limited to 'samples')
0 files changed, 0 insertions, 0 deletions