linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steve Dickson <SteveD@redhat.com>
To: Steve Dickson <steved@redhat.com>
Cc: Linux NFS Mailing list <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 1/3] mount.nfs: Continue to trying address when the server return ENOENT
Date: Tue, 27 Nov 2012 11:53:03 -0500	[thread overview]
Message-ID: <50B4EFEF.1060504@RedHat.com> (raw)
In-Reply-To: <1353961029-6317-1-git-send-email-steved@redhat.com>

Hello,

On 26/11/12 15:17, Steve Dickson wrote:
> With recent changes to the /etc/hosts file, the 'localhost'
> is now multiply defined as both an IPv4 address (127.0.01)
> and an IPv6 address (::1). This change causes first address
> returned by getaddrinfo('localhost') to be the IPv6 address
> instead of the IPv4 address.
> 
> The change in the default 'localhost' address type causes
> existing exports using '127.0.0.1' to fail, because the
> '::1' address is tried first and fails. The problem
> being not all the addresses that are returned by
> getaddrinfo('localhost') are tried.
> 
> So this patch allows that address list to continue to be
> process when the 'ENOENT' error is returned by the server.
> 
> Signed-off-by: Steve Dickson <steved@redhat.com>
After further review and some chat on IRC (thanks Frank!) using
EACCES, instead of ENOENT, to cause the next address to be tried 
is much more straightforward and simpler... V2 is on the way...

steved.

      parent reply	other threads:[~2012-11-27 16:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-26 20:17 [PATCH 1/3] mount.nfs: Continue to trying address when the server return ENOENT Steve Dickson
2012-11-26 20:17 ` [PATCH 2/3] mount.nfs: error message clean up Steve Dickson
2012-11-26 20:17 ` [PATCH 3/3] mountd: Return ENOENT when an export does not exist Steve Dickson
2012-11-27 16:53 ` Steve Dickson [this message]

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=50B4EFEF.1060504@RedHat.com \
    --to=steved@redhat.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;
as well as URLs for NNTP newsgroup(s).