Date: Fri, 27 May 2011 22:05:10 +0000 (UTC) From: Rick Macklem <rmacklem@FreeBSD.org> To: cvs-src-old@freebsd.org Subject: cvs commit: src/sys/fs/nfs nfs_commonsubs.c nfs_var.h src/sys/fs/nfsclient nfs_clcomsubs.c nfs_clstate.c src/sys/fs/nfsserver nfs_nfsdsocket.c nfs_nfsdstate.c Message-ID: <201105272205.p4RM5UaB027083@repoman.freebsd.org>
index | next in thread | raw e-mail
rmacklem 2011-05-27 22:05:10 UTC
FreeBSD src repository
Modified files:
sys/fs/nfs nfs_commonsubs.c nfs_var.h
sys/fs/nfsclient nfs_clcomsubs.c nfs_clstate.c
sys/fs/nfsserver nfs_nfsdsocket.c nfs_nfsdstate.c
Log:
SVN rev 222389 on 2011-05-27 22:05:10Z by rmacklem
Fix the new NFS client so that it handles NFSv4 state
correctly during a forced dismount. This required that
the exclusive and shared (refcnt) sleep lock functions check
for MNTK_UMOUNTF before sleeping, so that they won't block
while nfscl_umount() is getting rid of the state. As
such, a "struct mount *" argument was added to the locking
functions. I believe the only remaining case where a forced
dismount can get hung in the kernel is when a thread is
already attempting to do a TCP connect to a dead server
when the krpc client structure called nr_client is NULL.
This will only happen just after a "mount -u" with options
that force a new TCP connection is done, so it shouldn't
be a problem in practice.
MFC after: 2 weeks
Revision Changes Path
1.12 +16 -3 src/sys/fs/nfs/nfs_commonsubs.c
1.29 +2 -2 src/sys/fs/nfs/nfs_var.h
1.4 +1 -1 src/sys/fs/nfsclient/nfs_clcomsubs.c
1.23 +78 -16 src/sys/fs/nfsclient/nfs_clstate.c
1.13 +3 -3 src/sys/fs/nfsserver/nfs_nfsdsocket.c
1.32 +9 -9 src/sys/fs/nfsserver/nfs_nfsdstate.c
help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201105272205.p4RM5UaB027083>