From: YAMAMOTO Takashi <yamamoto@valinux.co.jp>
To: phil@fifi.org
Cc: trond.myklebust@fys.uio.no, theonetruekenny@yahoo.com,
linux-kernel@vger.kernel.org, nfs@lists.sourceforge.net
Subject: Re: [NFS client] NFS locks not released on abnormal process termination
Date: Thu, 08 Jan 2004 19:47:24 +0900 [thread overview]
Message-ID: <1073558844.242410.4086.nullmailer@yamt.dyndns.org> (raw)
In-Reply-To: Your message of "09 Dec 2003 00:15:24 -0800" <87llpms8yr.fsf@ceramic.fifi.org>
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
next prev parent reply other threads:[~2004-01-08 10:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-06 4:48 [NFS client] NFS locks not released on abnormal process termination Kenny Simpson
2003-12-06 19:50 ` Philippe Troin
2003-12-08 3:39 ` Kenny Simpson
2003-12-08 5:16 ` Trond Myklebust
2003-12-08 17:32 ` Philippe Troin
2003-12-08 19:56 ` Trond Myklebust
2003-12-09 8:15 ` Philippe Troin
2003-12-09 8:42 ` Trond Myklebust
2003-12-09 18:46 ` Philippe Troin
2003-12-10 2:42 ` Kenny Simpson
2003-12-15 1:04 ` Kenny Simpson
2003-12-15 1:14 ` Trond Myklebust
2004-01-08 10:47 ` YAMAMOTO Takashi [this message]
2004-01-08 16:50 ` trond.myklebust
2004-01-09 2:56 ` [NFS] " YAMAMOTO Takashi
2004-01-09 3:40 ` trond.myklebust
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1073558844.242410.4086.nullmailer@yamt.dyndns.org \
--to=yamamoto@valinux.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=nfs@lists.sourceforge.net \
--cc=phil@fifi.org \
--cc=theonetruekenny@yahoo.com \
--cc=trond.myklebust@fys.uio.no \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).