From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Philippe Troin <phil@fifi.org>
Cc: Kenny Simpson <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: 09 Dec 2003 03:42:02 -0500 [thread overview]
Message-ID: <shsekvetmat.fsf@guts.uio.no> (raw)
In-Reply-To: <87llpms8yr.fsf@ceramic.fifi.org>
>>>>> " " == Philippe Troin <phil@fifi.org> writes:
> From my reading of the patch, it supersedes the old patch, and
> is only
> necessary on the client. Is also does not compile :-)
Yeah, I admit I didn't test it out...
> Here's an updated patch which does compile.
Thanks.
> I am still running tests, but so far it looks good (that is all
> locks are freed when a process with locks running on a NFS
> client is killed).
Good...
There are still 2 other issues with the generic POSIX locking code.
Both issues have to do with CLONE_VM and have been raised on
linux-kernel & linux-fsdevel. Unfortunately they met with no response,
so I'm unable to pursue...
Cheers,
Trond
next prev parent reply other threads:[~2003-12-09 8:44 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 [this message]
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
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=shsekvetmat.fsf@guts.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=linux-kernel@vger.kernel.org \
--cc=nfs@lists.sourceforge.net \
--cc=phil@fifi.org \
--cc=theonetruekenny@yahoo.com \
/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).