Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 25 Apr 2017 19:14:31 +0000 (UTC)
From:      Rick Macklem <rmacklem@FreeBSD.org>
To:        src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-stable@freebsd.org, svn-src-stable-11@freebsd.org
Subject:   svn commit: r317418 - stable/11/sys/fs/nfsclient
Message-ID:  <201704251914.v3PJEVQP035847@repo.freebsd.org>

next in thread | raw e-mail | index | archive | help
Author: rmacklem
Date: Tue Apr 25 19:14:31 2017
New Revision: 317418
URL: https://svnweb.freebsd.org/changeset/base/317418

Log:
  MFC: r316667
  Fix the NFSv4 client hndling of a stale write verifier in the Commit operation.
  
  When the NFSv4 client Commit operation encountered a stale write verifier,
  it erroneously mapped that to EIO. This could have caused recently written
  data to be lost when a server crashes/reboots between an UNSTABLE write
  and the subsequent commit. This patch fixes this.
  The bug was only for the NFSv4 client and did not affect NFSv3.

Modified:
  stable/11/sys/fs/nfsclient/nfs_clport.c
Directory Properties:
  stable/11/   (props changed)

Modified: stable/11/sys/fs/nfsclient/nfs_clport.c
==============================================================================
--- stable/11/sys/fs/nfsclient/nfs_clport.c	Tue Apr 25 19:02:34 2017	(r317417)
+++ stable/11/sys/fs/nfsclient/nfs_clport.c	Tue Apr 25 19:14:31 2017	(r317418)
@@ -1196,7 +1196,7 @@ nfscl_maperr(struct thread *td, int erro
 {
 	struct proc *p;
 
-	if (error < 10000)
+	if (error < 10000 || error >= NFSERR_STALEWRITEVERF)
 		return (error);
 	if (td != NULL)
 		p = td->td_proc;



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201704251914.v3PJEVQP035847>