From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Ben Greear <greearb@candelatech.com>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: RFC: support srcaddr= option to bind to local IPs.
Date: Tue, 07 Sep 2010 13:56:06 -0400 [thread overview]
Message-ID: <1283882166.2788.48.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <4C81449B.4010900@candelatech.com>
On Fri, 2010-09-03 at 11:55 -0700, Ben Greear wrote:
> This patch lets one bind the local side of NFS sockets to a particular
> IP address. This can be useful for users on multi-homed systems.
>
> This patch must be on top of the previous patch to fix the IPv6 address
> comparison or it will not work.
>
> Comments and suggestions welcome...I'll incorporate those and post an
> official signed-off patch after that.
>
> Thanks,
> Ben
>
The code in nfs_callback_authenticate is going to break NFSv4 callbacks.
Callbacks are sent to the -oclientaddr address, not srcaddr (btw, I
really dislike that new boolean argument to nfs_find_client(). If you
don't want to compare the source address, then have the caller pass a
NULL pointer).
As has been pointed out to you before, all this is very intrusive, and
you have yet to give a description of why it is useful, and better than
using private socket namespaces (which is what container virtualised
systems will be wanting). The latter can even ensure that it all works
for userspace applications (such as rpc.statd) too.
IOW: I'd be quite happy to take patches to support private namespaces
properly: afaics, we do need to make nfs_find_client aware of them, and
ditto for lockd and the NFSv4 callback channel.
I remain less than convinced that we need to be able to specify
per-mountpoint source addresses...
Trond
next prev parent reply other threads:[~2010-09-07 17:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-03 18:55 RFC: support srcaddr= option to bind to local IPs Ben Greear
2010-09-07 17:56 ` Trond Myklebust [this message]
2010-09-07 18:33 ` Ben Greear
2010-09-07 20:41 ` Ben Greear
2010-09-07 20:54 ` Trond Myklebust
2010-09-07 21:10 ` Ben Greear
2010-09-07 21:12 ` Trond Myklebust
2010-09-07 23: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=1283882166.2788.48.camel@heimdal.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=greearb@candelatech.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox