From: Chuck Lever <chuck.lever@oracle.com>
To: Neil Brown <neilb@suse.de>
Cc: nfs@lists.sourceforge.net, Steve Dickson <SteveD@redhat.com>
Subject: Re: [PATCH nfs-utils 1/3] probe_port should not try other versions in a version was explicitly given.
Date: Thu, 01 Nov 2007 12:29:37 -0400 [thread overview]
Message-ID: <4729FEF1.2070903@oracle.com> (raw)
In-Reply-To: <1193894817-20622-2-git-send-email-neilb@suse.de>
[-- Attachment #1: Type: text/plain, Size: 1572 bytes --]
Neil Brown wrote:
> Currently if probe port is asked to probe for a specific version, and
> that version is not supported, it will probe other versions too.
> This means that if mountd is run with "--no-nfs-version 3",
> It will first probe for NFS version 3, which will succeed (assuming the
> kernel supported NFSv3), then it will check the matching mountd version (3)
> and probe_port on discovering that isn't supported will try other versions,
> find "1" is supported will succeed.
>
> This leaves us using mount version 1 for an NFSv3 mount, which doesn't work
> and leads to a SIGSEGV
>
> There is no case where trying other versions is needed the request one is
> not supported, so simply remove that code.
I agree with that understanding: if the caller is asking for a specific
version of the protocol in question, we aren't looking for a wildcard.
Time to add another case to our list of regression tests.
I wonder if the same misbehavior occurs when probing for transport
protocols?
> Signed-off-by: Neil Brown <neilb@suse.de>
> ---
> utils/mount/network.c | 4 ----
> 1 files changed, 0 insertions(+), 4 deletions(-)
>
> diff --git a/utils/mount/network.c b/utils/mount/network.c
> index 63d5f5a..2b09457 100644
> --- a/utils/mount/network.c
> +++ b/utils/mount/network.c
> @@ -417,10 +417,6 @@ static int probe_port(clnt_addr_t *server, const unsigned long *versions,
> continue;
> p_prot = protos;
> }
> - if (vers == pmap->pm_vers) {
> - p_vers = versions;
> - vers = 0;
> - }
> if (vers || !*++p_vers)
> break;
> }
[-- Attachment #2: chuck.lever.vcf --]
[-- Type: text/x-vcard, Size: 259 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
version:2.1
end:vcard
[-- Attachment #3: Type: text/plain, Size: 314 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
next prev parent reply other threads:[~2007-11-01 16:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-01 5:26 [PATCH nfs-utils] probe_port should not try other versions in a version was explicitly given Neil Brown
2007-11-01 5:26 ` [PATCH nfs-utils 1/3] " Neil Brown
2007-11-01 5:26 ` [PATCH nfs-utils 2/3] Correctly probe mount v2 Neil Brown
2007-11-01 5:26 ` [PATCH nfs-utils 3/3] Fix bug in auto-exporting subordinate mounts Neil Brown
2007-11-05 9:54 ` Steve Dickson
2007-11-05 10:58 ` [PATCH nfs-utils 2/3] Correctly probe mount v2 Steve Dickson
2007-11-05 18:01 ` Peter Staubach
2007-11-01 16:29 ` Chuck Lever [this message]
2007-11-02 2:02 ` [PATCH nfs-utils 1/3] probe_port should not try other versions in a version was explicitly given Neil Brown
2007-11-02 17:01 ` Chuck Lever
2007-11-05 9:55 ` 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=4729FEF1.2070903@oracle.com \
--to=chuck.lever@oracle.com \
--cc=SteveD@redhat.com \
--cc=neilb@suse.de \
--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 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.