All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: linux-nfs@vger.kernel.org, Patrick McHardy <kaber@trash.net>
Subject: Re: PATCH:  Support binding to a local IPv4 address when mounting a server.
Date: Sat, 21 Feb 2009 22:24:41 -0800	[thread overview]
Message-ID: <49A0EFA9.6010602@candelatech.com> (raw)
In-Reply-To: <EF45429F-0B16-47C7-89ED-7C14C44E6E5E@oracle.com>

Chuck Lever wrote:
>
> Would lockd also need to have this information too (passed in via 
> nlmclnt_inet)?
I found an fs/lockd directory, but cannot find 'nlmclnt_inet' anywhere 
in the kernel or nfs-utils.

>
> Would we also want kernel rpcbind requests to be sensitive to the 
> passed-in bind address?

It seems from searching net/sunrpc dir that kernel_bind is called 
appropriately which should
bind the a local addr if correct information is passed in, at least.   
This must be working
(assuming NFS calls this code eventually) since I *am* getting at least 
most of the NFS traffic
correctly bound to the specified bindaddr.

I wouldn't be surprised if the binaddr isn't being configured in the 
lockd properly,
but I'm not yet sure of how to get that information to lockd since I 
just started looking
at that code...

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com> 
Candela Technologies Inc  http://www.candelatech.com



  parent reply	other threads:[~2009-02-22  6:24 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-22  1:01 PATCH: Support binding to a local IPv4 address when mounting a server Ben Greear
2009-01-22  2:38 ` Chuck Lever
2009-01-22  5:35   ` Ben Greear
2009-01-22 17:06     ` Chuck Lever
2009-01-22 17:31       ` Ben Greear
2009-01-23 17:18         ` Chuck Lever
2009-01-23 17:39           ` Ben Greear
2009-02-21  7:43           ` Ben Greear
2009-02-21 17:16             ` Trond Myklebust
2009-02-21 22:09             ` Chuck Lever
2009-02-22  5:52               ` Ben Greear
2009-02-22 19:09                 ` Trond Myklebust
     [not found]                   ` <1235329791.7331.75.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-02-22 20:29                     ` Chuck Lever
2009-02-22 22:01                       ` Trond Myklebust
2009-02-22 23:17                     ` Ben Greear
2009-02-22 23:41                       ` Trond Myklebust
     [not found]                         ` <1235346094.7331.111.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-02-22 23:45                           ` Ben Greear
2009-02-22  6:24               ` Ben Greear [this message]
2009-02-22 20:01                 ` Chuck Lever
2009-02-22  7:05               ` Ben Greear
  -- strict thread matches above, loose matches on Subject: below --
2009-02-21 18:18 Ben Greear

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=49A0EFA9.6010602@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=chuck.lever@oracle.com \
    --cc=kaber@trash.net \
    --cc=linux-nfs@vger.kernel.org \
    /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.