Linux NFS development
 help / color / mirror / Atom feed
From: Neil Brown <neilb@suse.de>
To: Steve Dickson <SteveD@redhat.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: [PATCH 09/11] nfs-utils: mount: Fixed mounts to multi-home	servers
Date: Tue, 27 Feb 2007 17:32:47 +1100	[thread overview]
Message-ID: <17891.53391.618228.526904@notabene.brown> (raw)
In-Reply-To: message from Steve Dickson on Monday February 26

On Monday February 26, SteveD@redhat.com wrote:
> commit 253c6b866a1ed4678c30131a41ef96821bae9d5f
> Author: Steve Dickson <steved@redhat.com>
> Date:   Sat Feb 24 16:08:22 2007 -0500
> 
>     Doing a connect on UDP sockets causes the Linux network
>     stack to reject UDP patches from multi-home server with
>     nic on the same subnet which caused mounts to hang.
>     
>     Signed-off-by: Steve Dickson <steved@redhat.com>
> 
> diff --git a/support/nfs/conn.c b/support/nfs/conn.c
> index 89f7676..06afcc4 100644
> --- a/support/nfs/conn.c
> +++ b/support/nfs/conn.c
> @@ -98,7 +98,7 @@ int get_socket(struct sockaddr_in *saddr, u_int p_prot, int resvp)
>  			return RPC_ANYSOCK;
>  		}
>  	}
> -	if (type == SOCK_STREAM || type == SOCK_DGRAM) {
> +	if (type == SOCK_STREAM) {

You are reverting a change from commit
   c2db41e8abb6ddc9d03a0c91c6db043fa0f85a8f

This was needed so we could find our local address to get the
call-back address sent to the server right for NFSv4.

I think the correct thing to do here is to fix mountd so that it
replies from the correct address.  Careful use of IP_PKTINFO makes
this fairly easy to manage.... except that the recvfrom and sendto
code is buried inside libc.... but if memory serves, that was fixed to
get this right some time ago.

What OS is running on this multi-homed server??

Maybe we have to do something ghastly like disconnect the socket after
getting the local address...  I hope not.

NeilBrown

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2007-02-27  6:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-26 11:18 [PATCH 09/11] nfs-utils: mount: Fixed mounts to multi-home servers Steve Dickson
2007-02-27  6:32 ` Neil Brown [this message]
2007-02-27 18:12   ` Jeff Layton
2007-03-01  1:48     ` Neil Brown
2007-03-11 19:58       ` Jeff Layton
2007-03-11 22:38         ` Neil Brown

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=17891.53391.618228.526904@notabene.brown \
    --to=neilb@suse.de \
    --cc=SteveD@redhat.com \
    --cc=nfs@lists.sourceforge.net \
    /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