From: YAMAMOTO Takashi <yamamoto@valinux.co.jp>
Subject: Re: [NFS client] NFS locks not released on abnormal process
 termination
Date: Thu, 08 Jan 2004 19:47:24 +0900
Sender: nfs-admin@lists.sourceforge.net
Message-ID: <1073558844.242410.4086.nullmailer@yamt.dyndns.org>
References: <87llpms8yr.fsf@ceramic.fifi.org>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Cc: trond.myklebust@fys.uio.no, theonetruekenny@yahoo.com,
	linux-kernel@vger.kernel.org, nfs@lists.sourceforge.net
To: phil@fifi.org
In-Reply-To: Your message of "09 Dec 2003 00:15:24 -0800"
	<87llpms8yr.fsf@ceramic.fifi.org>
Errors-To: nfs-admin@lists.sourceforge.net

hi,

> +	status = nlmclnt_proc(inode, cmd, fl);
> +	/* If we were signalled we still need to ensure that
> +	 * we clean up any state on the server. We therefore
> +	 * record the lock call as having succeeded in order to
> +	 * ensure that locks_remove_posix() cleans it out when
> +	 * the process exits.
> +	 */
> +	if (status == -EINTR || status == -ERESTARTSYS)
> +		posix_lock_file(filp, fl, 0);
> +	unlock_kernel();
> +	if (status < 0)
> +		return status;

i think it's problematic because you can't assume the lock was
granted on the server and the signaled process might not exit immediately.

YAMAMOTO Takashi


-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs