Linux NFS development
 help / color / mirror / Atom feed
From: Steve Dickson <SteveD@redhat.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH] nfsidmap: keyring_clear() should succeed if id_resolver keyring not found
Date: Sat, 12 Dec 2015 07:11:31 -0500	[thread overview]
Message-ID: <566C0EF3.2030606@RedHat.com> (raw)
In-Reply-To: <20151202212010.5614.82182.stgit@manet.1015granger.net>



On 12/02/2015 04:20 PM, Chuck Lever wrote:
> root#nfsvmb10:~# nfsidmap -c
> nfsidmap: 'id_resolver' keyring was not found.
> root#nfsvmb10:~# echo $?
> 1
> 
> If the id_resolver keyring doesn't exist, the kernel has no cached
> idmap information to expunge. AFAIK it's not an error.
> 
> If nfsidmap is run by a non-privileged user, the id_resolver keyring
> is never visible. IMO that should be reported, but the error message
> should report the privilege problem, not the missing keyring.
> 
> Reported-by: Amy Shi <amy.shi@oracle.com>
> Fixes: 69aa69e7de80 ('nfsidmap: Allow keys to be cleared from the ')
> Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Committed... 

steved.

> ---
>  utils/nfsidmap/nfsidmap.c |   13 +++++++++----
>  1 file changed, 9 insertions(+), 4 deletions(-)
> 
> diff --git a/utils/nfsidmap/nfsidmap.c b/utils/nfsidmap/nfsidmap.c
> index 507193b..15b4a51 100644
> --- a/utils/nfsidmap/nfsidmap.c
> +++ b/utils/nfsidmap/nfsidmap.c
> @@ -80,8 +80,9 @@ static int keyring_clear(const char *keyring)
>  
>  	key = find_key_by_type_and_desc("keyring", keyring, 0);
>  	if (key == -1) {
> -		xlog_err("'%s' keyring was not found.", keyring);
> -		return EXIT_FAILURE;
> +		if (verbose)
> +			xlog_warn("'%s' keyring was not found.", keyring);
> +		return EXIT_SUCCESS;
>  	}
>  
>  	if (keyctl_clear(key) < 0) {
> @@ -89,10 +90,9 @@ static int keyring_clear(const char *keyring)
>  				(unsigned int)key);
>  		return EXIT_FAILURE;
>  	}
> -	
> +
>  	if (verbose)
>  		xlog_warn("'%s' cleared", keyring);
> -
>  	return EXIT_SUCCESS;
>  }
>  
> @@ -404,6 +404,11 @@ int main(int argc, char **argv)
>  		}
>  	}
>  
> +	if (geteuid() != 0) {
> +		xlog_err("Must be run as root.");
> +		return EXIT_FAILURE;
> +	}
> +
>  	if ((rc = nfs4_init_name_mapping(PATH_IDMAPDCONF)))  {
>  		xlog_errno(rc, "Unable to create name to user id mappings.");
>  		return EXIT_FAILURE;
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

  reply	other threads:[~2015-12-12 12:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-02 21:20 [PATCH] nfsidmap: keyring_clear() should succeed if id_resolver keyring not found Chuck Lever
2015-12-12 12:11 ` Steve Dickson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-12-02 21:23 Chuck Lever

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=566C0EF3.2030606@RedHat.com \
    --to=steved@redhat.com \
    --cc=chuck.lever@oracle.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