NFS: commit direct writes even if they fail partially
authorJ. Bruce Fields <bfields@redhat.com>
Tue, 16 Jan 2018 15:08:00 +0000 (10:08 -0500)
committerTrond Myklebust <trond.myklebust@primarydata.com>
Tue, 16 Jan 2018 15:13:23 +0000 (10:13 -0500)
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>
Cc: stable@vger.kernel.org
Signed-off-by: Trond Myklebust <trond.myklebust@primarydata.com>
fs/nfs/direct.c

index d2972d5374695050cdc3598f6488510af87b3379..8c10b0562e75d2fb0b3c92fe0628d3a79fede48b 100644 (file)
@@ -775,10 +775,8 @@ static void nfs_direct_write_completion(struct nfs_pgio_header *hdr)
 
        spin_lock(&dreq->lock);
 
-       if (test_bit(NFS_IOHDR_ERROR, &hdr->flags)) {
-               dreq->flags = 0;
+       if (test_bit(NFS_IOHDR_ERROR, &hdr->flags))
                dreq->error = hdr->error;
-       }
        if (dreq->error == 0) {
                nfs_direct_good_bytes(dreq, hdr);
                if (nfs_write_need_commit(hdr)) {