From: Philippe Troin <phil@fifi.org>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
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: 08 Dec 2003 09:32:05 -0800 [thread overview]
Message-ID: <877k17rzai.fsf@ceramic.fifi.org> (raw)
In-Reply-To: <shszne3risb.fsf@charged.uio.no>
Trond Myklebust <trond.myklebust@fys.uio.no> writes:
> >>>>> " " == Kenny Simpson <theonetruekenny@yahoo.com> writes:
>
> > So, this patch has not found its way into any kernel yet? Is
> > there anyone actively persuing this bug?
>
> Feel free. There are only so many hours in a day, and right now
> mine are pretty much overbooked with NFSv4 stuff...
Please note that this fix only mitigates the bug: it can still occur,
but much less frequently. Before this patch, nfsd would loose track of
the lock (see the enclosed program at the beginning of the thread)
after a few (<5) kills. With the patch, it takes sometimes as many as
300~500 kills before the bugs manifests itself.
Trond, do you think I should push the patch to Marcelo, or should I
wait for a better fix? I don't think Marcelo would accept a partial
fix. I would try to fix it myself, but I have no clue on the inner
workings of lockd/nfsd.
Phil.
next prev parent reply other threads:[~2003-12-08 17:32 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 [this message]
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
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=877k17rzai.fsf@ceramic.fifi.org \
--to=phil@fifi.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nfs@lists.sourceforge.net \
--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).