Linux NFS development
 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] mount.nfs: submarvellous messages from mount.nfs
Date: Tue, 16 Aug 2011 12:46:57 -0400	[thread overview]
Message-ID: <4E4A9F01.2080305@RedHat.com> (raw)
In-Reply-To: <1313496159-4281-1-git-send-email-steved@redhat.com>



On 08/16/2011 08:02 AM, Steve Dickson wrote:
> From: Max Matveev <makc@redhat.com>
> 
> Consider a setup where mountd on the server is controlled via
> tcp_wrappers (usual RHEL setup) and will not process calls from a
> particular client because of something in /etc/hosts.deny.
> 
> When such client attempts to do v3 mount, the error message printed
> by mount.nfs is misleading.
> 
> This patch changes that error message from:
>     mount.nfs: Argument list too long
> to
>     mount.nfs: access denied by server while mounting server:/export
> 
> Signed-off-by: Steve Dickson <steved@redhat.com>
Committed...

steved.

> ---
>  utils/mount/stropts.c |    2 ++
>  1 files changed, 2 insertions(+), 0 deletions(-)
> 
> diff --git a/utils/mount/stropts.c b/utils/mount/stropts.c
> index f1aa503..4d023d6 100644
> --- a/utils/mount/stropts.c
> +++ b/utils/mount/stropts.c
> @@ -538,6 +538,8 @@ nfs_rewrite_pmap_mount_options(struct mount_options *options)
>  		errno = ESPIPE;
>  		if (rpc_createerr.cf_stat == RPC_PROGNOTREGISTERED)
>  			errno = EOPNOTSUPP;
> +		else if (rpc_createerr.cf_stat == RPC_AUTHERROR)
> +			errno = EACCES;
>  		else if (rpc_createerr.cf_error.re_errno != 0)
>  			errno = rpc_createerr.cf_error.re_errno;
>  		return 0;

      reply	other threads:[~2011-08-16 18:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-16 12:02 [PATCH] mount.nfs: submarvellous messages from mount.nfs Steve Dickson
2011-08-16 16:46 ` 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=4E4A9F01.2080305@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