[src/trunk]: src/sys/nfs Handle EWOULDBLOCK the same way as EPIPE. It seems t...

[bouyer <bouyer%NetBSD.org@localhost>]

details:   https://anonhg.NetBSD.org/src/rev/196c38dae60d
branches:  trunk
changeset: 748778:196c38dae60d
user:      bouyer <bouyer%NetBSD.org@localhost>
date:      Thu Nov 05 08:11:24 2009 +0000

description:
Handle EWOULDBLOCK the same way as EPIPE. It seems the TCP socket layer
can return EWOULDBLOCK on some occasion when the connection is broken.

diffstat:

 sys/nfs/nfs_socket.c |  6 +++---
 1 files changed, 3 insertions(+), 3 deletions(-)

diffs (27 lines):

diff -r 3971f8bc244a -r 196c38dae60d sys/nfs/nfs_socket.c
--- a/sys/nfs/nfs_socket.c      Thu Nov 05 07:46:10 2009 +0000
+++ b/sys/nfs/nfs_socket.c      Thu Nov 05 08:11:24 2009 +0000
@@ -1,4 +1,4 @@
-/*     $NetBSD: nfs_socket.c,v 1.181 2009/10/16 23:36:05 pooka Exp $   */
+/*     $NetBSD: nfs_socket.c,v 1.182 2009/11/05 08:11:24 bouyer Exp $  */
 
 /*
  * Copyright (c) 1989, 1991, 1993, 1995
@@ -39,7 +39,7 @@
  */
 
 #include <sys/cdefs.h>
-__KERNEL_RCSID(0, "$NetBSD: nfs_socket.c,v 1.181 2009/10/16 23:36:05 pooka Exp $");
+__KERNEL_RCSID(0, "$NetBSD: nfs_socket.c,v 1.182 2009/11/05 08:11:24 bouyer Exp $");
 
 #ifdef _KERNEL_OPT
 #include "fs_nfs.h"
@@ -1145,7 +1145,7 @@
        /*
         * Wait for the reply from our send or the timer's.
         */
-       if (!error || error == EPIPE)
+       if (!error || error == EPIPE || error == EWOULDBLOCK)
                error = nfs_reply(rep, lwp);
 
        /*