From: Steve Dickson <SteveD@RedHat.com>
To: Srikrishan Malik <srikrishanmalik@gmail.com>, linux-nfs@vger.kernel.org
Subject: Re: [PATCH] nfsidmap:umich_ldap return success only if attributes are found in ldap resp.
Date: Fri, 18 Sep 2020 14:31:37 -0400 [thread overview]
Message-ID: <89e9790c-d2fc-6b2f-cc2a-6e036a75419f@RedHat.com> (raw)
In-Reply-To: <20200911142202.84696-1-srikrishanmalik@gmail.com>
On 9/11/20 10:22 AM, Srikrishan Malik wrote:
> Return ENOENT if the UID/GID attributes are not found in ldap response.
>
> Signed-off-by: Srikrishan Malik <srikrishanmalik@gmail.com>
Committed... (tag nfs-utils-2-5-2-rc5)
steved.
> ---
> support/nfsidmap/umich_ldap.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/support/nfsidmap/umich_ldap.c b/support/nfsidmap/umich_ldap.c
> index c475d379..1aa2af49 100644
> --- a/support/nfsidmap/umich_ldap.c
> +++ b/support/nfsidmap/umich_ldap.c
> @@ -643,6 +643,7 @@ umich_name_to_ids(char *name, int idtype, uid_t *uid, gid_t *gid,
> goto out_memfree;
> }
> *uid = tmp_uid;
> + err = 0;
> } else if (strcasecmp(attr_res, ldap_map.NFSv4_gid_attr) == 0) {
> tmp_g = strtoul(*idstr, (char **)NULL, 10);
> tmp_gid = tmp_g;
> @@ -656,6 +657,7 @@ umich_name_to_ids(char *name, int idtype, uid_t *uid, gid_t *gid,
> goto out_memfree;
> }
> *gid = tmp_gid;
> + err = 0;
> } else {
> IDMAP_LOG(0, ("umich_name_to_ids: received attr "
> "'%s' ???", attr_res));
> @@ -667,7 +669,6 @@ umich_name_to_ids(char *name, int idtype, uid_t *uid, gid_t *gid,
> ldap_value_free(idstr);
> }
>
> - err = 0;
> out_memfree:
> ber_free(ber, 0);
> out_unbind:
>
prev parent reply other threads:[~2020-09-18 18:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-11 14:22 [PATCH] nfsidmap:umich_ldap return success only if attributes are found in ldap resp Srikrishan Malik
2020-09-18 18:31 ` 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=89e9790c-d2fc-6b2f-cc2a-6e036a75419f@RedHat.com \
--to=steved@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=srikrishanmalik@gmail.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;
as well as URLs for NNTP newsgroup(s).