From: Wendy Cheng <s.wendy.cheng@gmail.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>, linux-nfs@vger.kernel.org
Subject: Re: lock reclaims outside grace period
Date: Tue, 29 Apr 2008 19:45:07 -0500 [thread overview]
Message-ID: <4817C113.2000603@gmail.com> (raw)
In-Reply-To: <20080430000349.GA32692@fieldses.org>
J. Bruce Fields wrote:
> On Tue, Apr 29, 2008 at 03:18:51PM -0700, Trond Myklebust wrote:
>
>> On Tue, 2008-04-29 at 17:57 -0400, J. Bruce Fields wrote:
>>
>>> Current lockd code appears to reject regular locks done during the grace
>>> period, but not reclaims that come outside of the grace period.
>>>
>>> (That's based on inspecting the code--I haven't run tests.)
>>>
>>> That seems like an obvious bug. (We're not giving the client any way to
>>> determine whether conflicting locks might have been granted.)
>>>
>>> Can we fix it, or is there a chance that people have been depending on
>>> this behavior? (Maybe for failing over to an already-active server??)
>>>
>> Sorry, but I really don't care if anyone has been relying on it: that is
>> a _major_ bug and needs to be fixed ASAP.
>>
>
> OK, good, I'll do some tests to confirm and then submit a patch.
>
I can't disagree - but do prepare people start to ask why after kernel
version 2.6.x, they have to extend grace period to get NFS locking works
:) ...
-- Wendy
next prev parent reply other threads:[~2008-04-30 0:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-29 21:57 lock reclaims outside grace period J. Bruce Fields
2008-04-29 22:18 ` Trond Myklebust
[not found] ` <1209507531.8321.11.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2008-04-30 0:03 ` J. Bruce Fields
2008-04-30 0:45 ` Wendy Cheng [this message]
2008-05-02 20:04 ` J. Bruce Fields
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=4817C113.2000603@gmail.com \
--to=s.wendy.cheng@gmail.com \
--cc=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--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