All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frank van Maarseveen <frankvm@frankvm.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Frank van Maarseveen <frankvm@frankvm.com>,
	"Mr. Charles Edward Lever" <Chuck.Lever@oracle.com>,
	"J. Bruce Fields" <bfields@fieldses.org>,
	Linux NFS mailing list <linux-nfs@vger.kernel.org>
Subject: Re: [NLM] 2.6.27.14 breakage when grace period expires
Date: Thu, 12 Feb 2009 20:16:07 +0100	[thread overview]
Message-ID: <20090212191607.GA3108@janus> (raw)
In-Reply-To: <1234465837.7190.62.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 2007 bytes --]

On Thu, Feb 12, 2009 at 02:10:37PM -0500, Trond Myklebust wrote:
> On Thu, 2009-02-12 at 19:29 +0100, Frank van Maarseveen wrote:
> > On Thu, Feb 12, 2009 at 01:17:27PM -0500, Trond Myklebust wrote:
> > > On Thu, 2009-02-12 at 16:36 +0100, Frank van Maarseveen wrote:
> > > > A little theorizing:
> > > > If the unlock of a yet unrecovered lock has failed up to that point then
> > > > the client sure must remember the lock somehow. That might explain the
> > > > secondary error when a conflicting lock is granted by the server.
> > > 
> > > Sorry, but that doesn't hold water. The client will release the VFS
> > > 'mirror' of the lock before it attempts to unlock. Otherwise, you could
> > > have some nasty races between the unlock thread and the recovery
> > > thread...
> > > Besides, the granted callback handler on the client only checks the list
> > > of blocked locks for a match.
> > 
> > ok, then we have more than one NLM bug to resolve.
> > 
> > > 
> > > Oh, bugger, I know what this is... It's the same thing that happened to
> > > the NFSv4 callback server. If you compile with CONFIG_IPV6 or
> > > CONFIG_IPV6_MODULE enabled, and also set CONFIG_SUNRPC_REGISTER_V4, then
> > > the NLM server will listen on an IPv6 socket, and so the RPC request
> > > come in with their IPv4 address mapped into the IPv6 namespace.
> > 
> > Nope:
> > 
> > 	$ zgrep IPV6 /proc/config.gz 
> > 	# CONFIG_IPV6 is not set
> > 	$ zgrep SUNRPC /proc/config.gz 
> > 	CONFIG_SUNRPC=y
> > 	CONFIG_SUNRPC_GSS=y
> > 	# CONFIG_SUNRPC_BIND34 is not set
> 
> Sorry, yes... 2.6.27.x should be OK. The lockd v4mapped addresses bug is
> specific to 2.6.29. Chuck, are you planning on fixing this before
> 2.6.29-final comes out?
> 
> > And remember this is not a recent regression.
> 
> It would help if you sent us the full binary tcpdump, instead of just
> the summary. That should enable us to figure out which of the tests is
> failing in nlmclnt_grant().

I posted the link already. Anyway, see attachment.

-- 
Frank

[-- Attachment #2: 2.6.27.14-nlm-grace.pcap --]
[-- Type: application/octet-stream, Size: 33708 bytes --]

  parent reply	other threads:[~2009-02-12 19:16 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-11 11:23 [NLM] 2.6.27.14 breakage when grace period expires Frank van Maarseveen
2009-02-11 20:35 ` J. Bruce Fields
2009-02-11 20:37   ` Frank van Maarseveen
2009-02-11 20:39     ` J. Bruce Fields
2009-02-11 20:57       ` Frank van Maarseveen
2009-02-12 14:28       ` Frank van Maarseveen
2009-02-12 15:16         ` Trond Myklebust
     [not found]           ` <1234451789.7190.38.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-02-12 15:36             ` Frank van Maarseveen
2009-02-12 18:17               ` Trond Myklebust
     [not found]                 ` <1234462647.7190.53.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-02-12 18:29                   ` Frank van Maarseveen
2009-02-12 19:10                     ` Trond Myklebust
     [not found]                       ` <1234465837.7190.62.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-02-12 19:16                         ` Frank van Maarseveen [this message]
2009-02-12 20:24                           ` Trond Myklebust
     [not found]                             ` <1234470251.7190.102.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-02-13 11:04                               ` Frank van Maarseveen
2009-02-12 19:35                         ` Chuck Lever
2009-02-12 19:43                           ` Trond Myklebust
     [not found]                             ` <1234467795.7190.70.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-02-12 20:11                               ` Chuck Lever
2009-02-12 20:27                                 ` Trond Myklebust
     [not found]                                   ` <1234470457.7190.106.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-02-12 20:43                                     ` Chuck Lever
2009-02-12 20:54                                       ` Trond Myklebust
     [not found]                                         ` <1234472083.7190.124.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-02-12 21:43                                           ` Chuck Lever
2009-02-12 22:03                                             ` Trond Myklebust
2009-02-12 22:02                                       ` Trond Myklebust
     [not found]                                         ` <1234476134.7190.187.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-02-12 22:11                                           ` Chuck Lever
2009-02-12 22:19                                             ` 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=20090212191607.GA3108@janus \
    --to=frankvm@frankvm.com \
    --cc=Chuck.Lever@oracle.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 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.