From: "J. Bruce Fields" <bfields@fieldses.org>
To: Vivek Trivedi <vtrivedi018@gmail.com>
Cc: linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org,
Namjae Jeon <linkinjeon@gmail.com>
Subject: Re: [PATCH] nfsd4: fix cr_principal comparison check in same_creds
Date: Tue, 24 Jul 2012 12:53:53 -0400 [thread overview]
Message-ID: <20120724165353.GH8570@fieldses.org> (raw)
In-Reply-To: <1343144900-4522-1-git-send-email-vtrivedi018@gmail.com>
On Tue, Jul 24, 2012 at 09:18:20PM +0530, Vivek Trivedi wrote:
> This fixes a wrong check for same cr_principal in same_creds
Thanks for the fix.
Looks like I introduced that with
8fbba96e5b327665265ad02b7f331b68536828bf "nfsd4: stricter cred
comparison for setclientid/exchange_id".
Queuing for 3.6, cc'ing stable.
--b.
>
> Signed-off-by: Vivek Trivedi <vtrivedi018@gmail.com>
> Signed-off-by: Namjae Jeon <linkinjeon@gmail.com>
> ---
> fs/nfsd/nfs4state.c | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/fs/nfsd/nfs4state.c b/fs/nfsd/nfs4state.c
> index 94effd5..e8ead04 100644
> --- a/fs/nfsd/nfs4state.c
> +++ b/fs/nfsd/nfs4state.c
> @@ -1215,7 +1215,7 @@ static bool groups_equal(struct group_info *g1, struct group_info *g2)
> return true;
> }
>
> -static int
> +static bool
> same_creds(struct svc_cred *cr1, struct svc_cred *cr2)
> {
> if ((cr1->cr_flavor != cr2->cr_flavor)
> @@ -1227,7 +1227,7 @@ same_creds(struct svc_cred *cr1, struct svc_cred *cr2)
> return true;
> if (!cr1->cr_principal || !cr2->cr_principal)
> return false;
> - return 0 == strcmp(cr1->cr_principal, cr1->cr_principal);
> + return 0 == strcmp(cr1->cr_principal, cr2->cr_principal);
> }
>
> static void gen_clid(struct nfs4_client *clp)
> --
> 1.7.1
>
prev parent reply other threads:[~2012-07-24 16:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-24 15:48 [PATCH] nfsd4: fix cr_principal comparison check in same_creds Vivek Trivedi
2012-07-24 16:53 ` J. Bruce Fields [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=20120724165353.GH8570@fieldses.org \
--to=bfields@fieldses.org \
--cc=linkinjeon@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=vtrivedi018@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).