diff options
| author | J. Bruce Fields <bfields@redhat.com> | 2018-01-16 10:08:00 -0500 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2018-02-16 20:09:42 +0100 |
| commit | ae0499e7b11fe83717b0f3aebb436cdeabf5ba66 (patch) | |
| tree | c7543928cc8f6e020c5dac80a9e482320eb787dd /tools/perf/scripts/python/call-graph-from-postgresql.py | |
| parent | 79e10b1a8dbc3da57fae6fef90f4112e65b3d214 (diff) | |
NFS: commit direct writes even if they fail partially
commit 1b8d97b0a837beaf48a8449955b52c650a7114b4 upstream.
If some of the WRITE calls making up an O_DIRECT write syscall fail,
we neglect to commit, even if some of the WRITEs succeed.
We also depend on the commit code to free the reference count on the
nfs_page taken in the "if (request_commit)" case at the end of
nfs_direct_write_completion(). The problem was originally noticed
because ENOSPC's encountered partway through a write would result in a
closed file being sillyrenamed when it should have been unlinked.
Signed-off-by: J. Bruce Fields <bfields@redhat.com>
Signed-off-by: Trond Myklebust <trond.myklebust@primarydata.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions
