From owner-cvs-all Tue Apr 16 18: 7:38 2002 Delivered-To: cvs-all@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 8454337B404; Tue, 16 Apr 2002 18:07:30 -0700 (PDT) Received: (from iedowse@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g3H17U999882; Tue, 16 Apr 2002 18:07:30 -0700 (PDT) (envelope-from iedowse) Message-Id: <200204170107.g3H17U999882@freefall.freebsd.org> From: Ian Dowse Date: Tue, 16 Apr 2002 18:07:30 -0700 (PDT) To: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: cvs commit: src/sys/sys mount.h src/sys/kern vfs_syscalls.c src/sys/nfsclient nfs_socket.c X-FreeBSD-CVS-Branch: HEAD Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG iedowse 2002/04/16 18:07:30 PDT Modified files: sys/sys mount.h sys/kern vfs_syscalls.c sys/nfsclient nfs_socket.c Log: The recent NFS forced unmount improvements introduced a side-effect where some client operations might be unexpectedly cancelled during an unsuccessful non-forced unmount attempt. This causes problems for amd(8), because it periodically attempts a non-forced unmount to check if the filesystem is still in use. Fix this by adding a new mountpoint flag MNTK_UNMOUNTF that is set only during the operation of a forced unmount. Use this instead of MNTK_UNMOUNT to trigger the cancellation of hung NFS operations. Also correct a problem where dounmount() might inadvertently clear the MNTK_UNMOUNT flag. Reported by: simokawa MFC after: 1 week Revision Changes Path 1.247 +9 -2 src/sys/kern/vfs_syscalls.c 1.78 +4 -4 src/sys/nfsclient/nfs_socket.c 1.124 +6 -0 src/sys/sys/mount.h To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message