All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chuck Lever <chuck.lever@oracle.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: neilb@suse.de, nfs@lists.sourceforge.net
Subject: Re: [PATCH] mount.nfs: restore admin-specified clientaddr	option
Date: Thu, 30 Aug 2007 15:23:25 -0400	[thread overview]
Message-ID: <46D7192D.9090904@oracle.com> (raw)
In-Reply-To: <1188500090.7891.8.camel@gaula.trondhjem.org>

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

Trond Myklebust wrote:
> 'clientaddr' was set up because there is no way for the kernel (or an
> automated userland mount program) to determine exactly which IP address
> the server should be using for callbacks in the case where there are
> more than 1 options.
> That all depends on the local network topology, and routing policies,
> which may not be visible to the client.

The patch corrects a mistaken assumption I made while working on the 
text-based mount implementation.  The broken behavior is only a week or 
so old, doesn't affect legacy nfs4_mount_data style mounts, and was 
never part of an nfs-utils release.

It would be wonderful if we had some of these requirements written down 
somewhere, so we wouldn't be dependent on individuals who are 
unavailable at times when we need some historical perspective.  I've 
started doing this here:

http://wiki.linux-nfs.org/wiki/index.php/NewMountDesignSpec

You have to admit that existing mount option documentation is pretty 
scant on history and rationale.  Look at what nfs(5) says about 
clientaddr= :

> clientaddr=n   On a multi-homed client, this causes the client to use a
>                specific callback address when communicating with an NFS
>                version 4 server.  This option is currently ignored.

"This option is currently ignored."  Ummm....

And Neil just fixed the "multi-homed" part of mount's automated 
clientaddr generation.

And nfs(5) doesn't say Jack about NAT routers or network topology or 
routing policies.

I will send in a patch that also corrects nfs(5).

[-- Attachment #2: chuck.lever.vcf --]
[-- Type: text/x-vcard, Size: 290 bytes --]

begin:vcard
fn:Chuck Lever
n:Lever;Chuck
org:Oracle Corporation;Corporate Architecture: Linux Projects Group
adr:;;1015 Granger Avenue;Ann Arbor;MI;48104;USA
title:Principal Member of Staff
tel;work:+1 248 614 5091
x-mozilla-html:FALSE
url:http://oss.oracle.com/~cel
version:2.1
end:vcard


[-- Attachment #3: Type: text/plain, Size: 315 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

[-- Attachment #4: Type: text/plain, Size: 140 bytes --]

_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2007-08-30 19:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-30 17:46 [PATCH] mount.nfs: restore admin-specified clientaddr option Chuck Lever
2007-08-30 18:54 ` Trond Myklebust
2007-08-30 19:23   ` Chuck Lever [this message]
2007-08-30 22:41     ` 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=46D7192D.9090904@oracle.com \
    --to=chuck.lever@oracle.com \
    --cc=neilb@suse.de \
    --cc=nfs@lists.sourceforge.net \
    --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.