From: Philippe Troin <phil@fifi.org>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: nfs@lists.sourceforge.net
Subject: Re: Killed process on NFS client can result in lost lock on server
Date: 30 Sep 2003 23:38:20 -0700 [thread overview]
Message-ID: <87pthhv4wz.fsf@ceramic.fifi.org> (raw)
In-Reply-To: <87n0cl29cp.fsf@ceramic.fifi.org>
Philippe Troin <phil@fifi.org> writes:
> Trond Myklebust <trond.myklebust@fys.uio.no> writes:
>
> > >>>>> " " == Philippe Troin <phil@fifi.org> writes:
> >
> > > While trying to make this test program, I've noticed that the
> > > problem only occurs while I/O is done on the locked file. Note
> > > the write() in a while loop in the test program. I could not
> > > get the bad behavior to show up if no I/O is going on.
> >
> > Yep. It's the same problem as in nlmclnt_proc(): we have to clean up
> > all locks come rain or shine when the process exits.
>
> Thanks for the patch Trond, I'll give it a shot later today.
Unfortunately, your patch does not fix the bug, although it makes it
less frequent. Please try running kill-locks for extended periods of
time to see the bug happen again. I can see the problem develop after
100-200 successful locking attempts here, versus just a few (< 10)
successful locking attempts before your patch.
Phil.
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2003-10-01 6:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-30 20:06 Killed process on NFS client can result in lost lock on server Philippe Troin
2003-09-30 20:52 ` Trond Myklebust
2003-09-30 22:35 ` Philippe Troin
2003-09-30 22:36 ` Trond Myklebust
2003-10-01 6:38 ` Philippe Troin [this message]
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=87pthhv4wz.fsf@ceramic.fifi.org \
--to=phil@fifi.org \
--cc=nfs@lists.sourceforge.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.