Linux NFS development
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Wendy Cheng <wcheng@netapp.com>,
	Bob Bell
	<b_linuxnfs-Y/+76LoPTq9wBoktGHYdvgC/G2K4zDHf@public.gmane.org>,
	NFS list <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 0/2] NLM failover unlock
Date: Fri, 15 Feb 2008 11:36:59 -0500	[thread overview]
Message-ID: <20080215163659.GD20826@fieldses.org> (raw)
In-Reply-To: <755EF02D-A01D-409C-B695-E26F9A4A22BF@oracle.com>

On Fri, Feb 15, 2008 at 11:30:04AM -0500, Chuck Lever wrote:
> On Feb 15, 2008, at 11:20 AM, J. Bruce Fields wrote:
>> On Thu, Feb 14, 2008 at 02:04:28PM -0500, Wendy Cheng wrote:
>>> Bob Bell wrote:
>>>> On Mon, Jan 07, 2008 at 12:31:09AM -0500, Wendy Cheng wrote:
>>>>> This submission is part of the patch sets added to support NFS  
>>>>> server
>>>>> failover where the specified export is moved from one physical  
>>>>> server
>>>>> to another.
>>>>
>>>> Wendy,
>>>>
>>>> What's the current status of these patches?  I believe I have a
>>>> situation that could benefit from being able to release all NLM  
>>>> locks
>>>> on an exported filesystem.
>>>>
>>> I think Bruce has queued the unlock patch for 2.6.26 (Bruce ?) ..
>>
>> Not yet, for several reasons.  First, there's two smaller problems
>> outstanding that I can recall:
>>
>> 	- We should be matching on the superblock, not the vfs mount.
>> 	  Otherwise, for example, the unlock will have no effect if it's
>> 	  done from a private namespace, which I think will be
>> 	  unexpected.  Arguably this could result in revoking more locks
>> 	  than necessary, but if the goal is to allow unmounting some
>> 	  shared block device, then that's what we've got to do.
>> 	- Let's get the address types right.  I think the concensus from
>> 	  previous discussions was just to use in6_addr everywhere?
>
> I thought the consensus was use in_addr everywhere, and let me worry  
> about converting these to in6_addr as part of the NLM IPv6 work.

OK, that'd be fine too.

--b.

  reply	other threads:[~2008-02-15 16:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-07  5:31 [PATCH 0/2] NLM failover unlock Wendy Cheng
2008-02-14 18:38 ` Bob Bell
     [not found]   ` <20080214183833.GA26936-y89O8yXFYpDSsb2jM9SCN5/hYUUxywnI@public.gmane.org>
2008-02-14 19:04     ` Wendy Cheng
2008-02-15 16:20       ` J. Bruce Fields
2008-02-15 16:30         ` Chuck Lever
2008-02-15 16:36           ` J. Bruce Fields [this message]
2008-02-15 17:25         ` Wendy Cheng

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=20080215163659.GD20826@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=b_linuxnfs-Y/+76LoPTq9wBoktGHYdvgC/G2K4zDHf@public.gmane.org \
    --cc=chuck.lever@oracle.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=wcheng@netapp.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