From: Trond Myklebust <Trond.Myklebust@netapp.com>
To: Stanislav Kinsbursky <skinsbursky@parallels.com>
Cc: linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] NFS: suppressing showing of default mount port value in /proc fixed
Date: Tue, 07 Dec 2010 17:30:11 -0500 [thread overview]
Message-ID: <1291761011.3049.46.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <20101206085553.2172.24863.stgit@localhost6.localdomain6>
On Mon, 2010-12-06 at 12:00 +0300, Stanislav Kinsbursky wrote:
> Update: added check for zero value as it was before (note: can't simply check
> mountd_port for positive value because it's typeof unsigned short)
>
> Default value for mount server port is set to NFS_UNSPEC_PORT (-1) and will not
> be changed during parsing mount options for mound data version 6. This default
> value will be showed for mountport in /proc/mounts always since current default
> check is for zero value. This small mistake leads to big problem, because
> during umount.nfs execution from old user-space utils (at least nfs-utils
> 1.0.9) this value will be used as the server port to connect to. This request
> will be rejected (since port is 65535) and thus nfs mount point can't be
> unmounted.
>
> Note from Chuck Lever (chuck.lever@oracle.com): this is only possible if
> /etc/mtab is a link to /proc/mounts. Not all systems have this configuration.
>
> ---
> fs/nfs/super.c | 4 +++-
> 1 files changed, 3 insertions(+), 1 deletions(-)
>
> diff --git a/fs/nfs/super.c b/fs/nfs/super.c
> index 6d6e21d..449024f 100644
> --- a/fs/nfs/super.c
> +++ b/fs/nfs/super.c
> @@ -681,7 +681,9 @@ static void nfs_show_mountd_options(struct seq_file *m, struct nfs_server *nfss,
>
> if (nfss->mountd_version || showdefaults)
> seq_printf(m, ",mountvers=%u", nfss->mountd_version);
> - if (nfss->mountd_port || showdefaults)
> + if ((nfss->mountd_port &&
> + nfss->mountd_port != (unsigned short)NFS_UNSPEC_PORT) ||
> + showdefaults)
> seq_printf(m, ",mountport=%u", nfss->mountd_port);
>
> nfs_show_mountd_netid(m, nfss, showdefaults);
>
This patch needs a 'Signed-off-by:' before I can apply it.
Cheers
Trond
--
Trond Myklebust
Linux NFS client maintainer
NetApp
Trond.Myklebust@netapp.com
www.netapp.com
prev parent reply other threads:[~2010-12-07 22:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-06 9:00 Stanislav Kinsbursky
2010-12-07 22:30 ` Trond Myklebust [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=1291761011.3049.46.camel@heimdal.trondhjem.org \
--to=trond.myklebust@netapp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=skinsbursky@parallels.com \
/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
all inboxes | Powered by JetHome®