From: Simo Sorce <simo@redhat.com>
To: Scott Mayhew <smayhew@redhat.com>
Cc: bfields@fieldses.org, linux-nfs@vger.kernel.org
Subject: Re: [PATCH] svcrpc: fix potential GSSX_ACCEPT_SEC_CONTEXT decoding failures
Date: Tue, 28 Apr 2015 17:09:25 -0400 [thread overview]
Message-ID: <1430255365.13607.165.camel@willson.usersys.redhat.com> (raw)
In-Reply-To: <1430252993-20091-1-git-send-email-smayhew@redhat.com>
Thanks Scott,
I think this will help with older GSS-Proxy versions, in the newer
versions we are simply suppressing the exported composite name as the
kernel has no use for it.
Simo.
On Tue, 2015-04-28 at 16:29 -0400, Scott Mayhew wrote:
> In an environment where the KDC is running Active Directory, the
> exported composite name field returned in the context could be large
> enough to span a page boundary. Attaching a scratch buffer to the
> decoding xdr_stream helps deal with those cases.
>
> Signed-off-by: Scott Mayhew <smayhew@redhat.com>
> ---
> net/sunrpc/auth_gss/gss_rpc_xdr.c | 23 ++++++++++++++++-------
> 1 file changed, 16 insertions(+), 7 deletions(-)
>
> diff --git a/net/sunrpc/auth_gss/gss_rpc_xdr.c b/net/sunrpc/auth_gss/gss_rpc_xdr.c
> index 1ec19f6..eeeba5a 100644
> --- a/net/sunrpc/auth_gss/gss_rpc_xdr.c
> +++ b/net/sunrpc/auth_gss/gss_rpc_xdr.c
> @@ -793,20 +793,26 @@ int gssx_dec_accept_sec_context(struct rpc_rqst *rqstp,
> {
> u32 value_follows;
> int err;
> + struct page *scratch;
> +
> + scratch = alloc_page(GFP_KERNEL);
> + if (!scratch)
> + return -ENOMEM;
> + xdr_set_scratch_buffer(xdr, page_address(scratch), PAGE_SIZE);
>
> /* res->status */
> err = gssx_dec_status(xdr, &res->status);
> if (err)
> - return err;
> + goto out_free;
>
> /* res->context_handle */
> err = gssx_dec_bool(xdr, &value_follows);
> if (err)
> - return err;
> + goto out_free;
> if (value_follows) {
> err = gssx_dec_ctx(xdr, res->context_handle);
> if (err)
> - return err;
> + goto out_free;
> } else {
> res->context_handle = NULL;
> }
> @@ -814,11 +820,11 @@ int gssx_dec_accept_sec_context(struct rpc_rqst *rqstp,
> /* res->output_token */
> err = gssx_dec_bool(xdr, &value_follows);
> if (err)
> - return err;
> + goto out_free;
> if (value_follows) {
> err = gssx_dec_buffer(xdr, res->output_token);
> if (err)
> - return err;
> + goto out_free;
> } else {
> res->output_token = NULL;
> }
> @@ -826,14 +832,17 @@ int gssx_dec_accept_sec_context(struct rpc_rqst *rqstp,
> /* res->delegated_cred_handle */
> err = gssx_dec_bool(xdr, &value_follows);
> if (err)
> - return err;
> + goto out_free;
> if (value_follows) {
> /* we do not support upcall servers sending this data. */
> - return -EINVAL;
> + err = -EINVAL;
> + goto out_free;
> }
>
> /* res->options */
> err = gssx_dec_option_array(xdr, &res->options);
>
> +out_free:
> + __free_page(scratch);
> return err;
> }
--
Simo Sorce * Red Hat, Inc * New York
next prev parent reply other threads:[~2015-04-28 21:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-28 20:29 [PATCH] svcrpc: fix potential GSSX_ACCEPT_SEC_CONTEXT decoding failures Scott Mayhew
2015-04-28 21:09 ` Simo Sorce [this message]
2015-04-29 15:38 ` J. Bruce Fields
2015-04-29 15:39 ` J. Bruce Fields
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=1430255365.13607.165.camel@willson.usersys.redhat.com \
--to=simo@redhat.com \
--cc=bfields@fieldses.org \
--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 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).