From: Steve Dickson <SteveD@redhat.com>
To: Kinglong Mee <kinglongmee@gmail.com>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
smayhew@redhat.com
Subject: Re: [PATCH] rpc.mountd: Remove duplicate and invalid secinfo setting
Date: Thu, 07 May 2015 10:17:30 -0400 [thread overview]
Message-ID: <554B73FA.8080106@RedHat.com> (raw)
In-Reply-To: <552FB045.80604@gmail.com>
On 04/16/2015 08:51 AM, Kinglong Mee wrote:
> NFSD return reply of client's SECINFO_NO_NAME request with four
> security information number as, 1 1 0 0
>
> It's caused by commit 4a1ad4aa30,
> "mountd: Enable all auth flavors on pseudofs exports"
>
> This patch removes duplicate secinfo and invalid secinfo (zero).
>
> Signed-off-by: Kinglong Mee <kinglongmee@gmail.com>
> ---
> support/nfs/exports.c | 2 +-
> utils/mountd/v4root.c | 3 +++
> 2 files changed, 4 insertions(+), 1 deletion(-)
Committed...
steved.
>
> diff --git a/support/nfs/exports.c b/support/nfs/exports.c
> index 761a046..0aea6f1 100644
> --- a/support/nfs/exports.c
> +++ b/support/nfs/exports.c
> @@ -408,7 +408,7 @@ int secinfo_addflavor(struct flav_info *flav, struct exportent *ep)
> struct sec_entry *p;
>
> for (p=ep->e_secinfo; p->flav; p++) {
> - if (p->flav == flav)
> + if (p->flav == flav || p->flav->fnum == flav->fnum)
> return p - ep->e_secinfo;
> }
> if (p - ep->e_secinfo >= SECFLAVOR_COUNT) {
> diff --git a/utils/mountd/v4root.c b/utils/mountd/v4root.c
> index 429ebb8..d521725 100644
> --- a/utils/mountd/v4root.c
> +++ b/utils/mountd/v4root.c
> @@ -69,6 +69,9 @@ set_pseudofs_security(struct exportent *pseudo, int flags)
> for (flav = flav_map; flav < flav_map + flav_map_size; flav++) {
> struct sec_entry *new;
>
> + if (!flav->fnum)
> + continue;
> +
> i = secinfo_addflavor(flav, pseudo);
> new = &pseudo->e_secinfo[i];
>
>
prev parent reply other threads:[~2015-05-07 14:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-16 12:51 [PATCH] rpc.mountd: Remove duplicate and invalid secinfo setting Kinglong Mee
2015-04-17 18:15 ` Scott Mayhew
2015-05-06 13:38 ` Kinglong Mee
2015-05-07 14:17 ` 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=554B73FA.8080106@RedHat.com \
--to=steved@redhat.com \
--cc=kinglongmee@gmail.com \
--cc=linux-nfs@vger.kernel.org \
--cc=smayhew@redhat.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 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.