From: Philippe Troin <phil@fifi.org>
To: "Chris Croswhite" <csc@cadence.com>
Cc: <linux-kernel@vger.kernel.org>, <nfs@lists.sourceforge.net>
Subject: Re: [NFS] Re: [NFS client] NFS locks not released on abnormal process termination
Date: 09 Dec 2003 11:26:48 -0800 [thread overview]
Message-ID: <87wu95u70n.fsf@ceramic.fifi.org> (raw)
In-Reply-To: <EE335453C5C57840823404C684F9F61702417581@exmbx01sj.cadence.com>
"Chris Croswhite" <csc@cadence.com> writes:
> Philippe,
>
> What patches are you refering to?
The one in <87llpms8yr.fsf@ceramic.fifi.org> named
linux-2.4.23-nfs-lock-race-2.patch
Here a link to MARC, since the sourceforge mailing list web page
sucks:
http://marc.theaimsgroup.com/?l=linux-nfs&m=107095817723325&w=2
Phil.
> -----Original Message-----
> From: Philippe Troin [mailto:phil@fifi.org]
> Sent: Tue 09-Dec-03 10:46
> To: Trond Myklebust
> Cc: Kenny Simpson; linux-kernel@vger.kernel.org; nfs@lists.sourceforge.net
> Subject: [NFS] Re: [NFS client] NFS locks not released on abnormal process termination
> Trond Myklebust <trond.myklebust@fys.uio.no> writes:
>
> > >>>>> " " == 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...
>
> I've ran test overnight on four boxen, and no locks were lost.
> I guess you can send this patch to Marcello now.
>
> I've tested with the enclosed program.
>
>
> > 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...
>
> Can we help? Pointers?
>
> Phil.
>
>
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: SF.net Giveback Program.
> Does SourceForge.net help you be more productive? Does it
> help you create better code? SHARE THE LOVE, and help us help
> YOU! Click Here: http://sourceforge.net/donate/
> _______________________________________________
> NFS maillist - NFS@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nfs
next parent reply other threads:[~2003-12-09 20:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <EE335453C5C57840823404C684F9F61702417581@exmbx01sj.cadence.com>
2003-12-09 19:26 ` Philippe Troin [this message]
2004-01-08 16:50 [NFS client] NFS locks not released on abnormal process termination 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=87wu95u70n.fsf@ceramic.fifi.org \
--to=phil@fifi.org \
--cc=csc@cadence.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nfs@lists.sourceforge.net \
/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).