From: Hamo <hamo.by@gmail.com>
To: linux-nfs@vger.kernel.org
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
chuck.lever@oracle.com
Subject: Re: [PATCH] nfs-utils: mount: really return from errno test
Date: Thu, 13 Oct 2011 10:05:19 +0800 [thread overview]
Message-ID: <CAO_0yfNAFXKLomOSUd=Pun2_9+sot_uYNqBLC3ek8D5y-Xfypg@mail.gmail.com> (raw)
In-Reply-To: <CAO_0yfPgXJJSZNDYXHBSt45J0WQsh5EQVUs0nBN4wb+NoT6hAQ@mail.gmail.com>
CC: Chuck Lever <chuck.lever@oracle.com>
On Tue, Oct 11, 2011 at 5:44 PM, Hamo <hamo.by@gmail.com> wrote:
> We should only try next address family if we meet ECONNREFUSED or EHOSTUNREACH
> for v4 or ECONNREFUSED or EOPNOTSUPP or EHOSTUNREACH for v3v2.
> Before, only a break in swich can not make the program out of for loop.
>
> Signed-off-by: Yang Bai <hamo.by@gmail.com>
> ---
> utils/mount/stropts.c | 6 ++++--
> 1 files changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/utils/mount/stropts.c b/utils/mount/stropts.c
> index 314a806..4032bf3 100644
> --- a/utils/mount/stropts.c
> +++ b/utils/mount/stropts.c
> @@ -665,9 +665,10 @@ static int nfs_try_mount_v3v2(struct nfsmount_info *mi)
> case EHOSTUNREACH:
> continue;
> default:
> - break;
> + goto out;
> }
> }
> +out:
> return ret;
> }
>
> @@ -751,9 +752,10 @@ static int nfs_try_mount_v4(struct nfsmount_info *mi)
> case EHOSTUNREACH:
> continue;
> default:
> - break;
> + goto out;
> }
> }
> +out:
> return ret;
> }
>
> --
> 1.7.1
>
--
"""
Keep It Simple,Stupid.
"""
Chinese Name: 白杨
Nick Name: Hamo
Homepage: http://hamobai.com/
GPG KEY ID: 0xA4691A33
Key fingerprint = 09D5 2D78 8E2B 0995 CF8E 4331 33C4 3D24 A469 1A33
next prev parent reply other threads:[~2011-10-13 2:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-11 9:44 [PATCH] nfs-utils: mount: really return from errno test Hamo
2011-10-13 2:05 ` Hamo [this message]
2011-10-13 14:53 ` Chuck Lever
2011-10-13 16:34 ` Steve Dickson
2011-10-13 16:37 ` Chuck Lever
2011-10-13 16:59 ` Steve Dickson
2011-10-13 17:19 ` Trond Myklebust
2011-10-13 17:54 ` Chuck Lever
2011-10-13 19:03 ` Steve Dickson
2011-10-15 13:12 ` Hamo
2011-10-18 15:17 ` Steve Dickson
2011-10-18 16:08 ` Steve Dickson
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='CAO_0yfNAFXKLomOSUd=Pun2_9+sot_uYNqBLC3ek8D5y-Xfypg@mail.gmail.com' \
--to=hamo.by@gmail.com \
--cc=chuck.lever@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).