Kernel keyring development
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@kernel.org>
To: keyrings@vger.kernel.org
Subject: Re: [PATCH] KEYS: reuse keyring_index_key::desc_len in lookup_user_key()
Date: Thu, 10 Jan 2019 20:28:38 +0000	[thread overview]
Message-ID: <20190110202837.GD149637@gmail.com> (raw)

On Fri, Nov 02, 2018 at 07:10:49PM -0700, Eric Biggers wrote:
> From: Eric Biggers <ebiggers@google.com>
> 
> When lookup_user_key() checks whether the key is possessed, it should
> use the key's existing index_key including the 'desc_len' field, rather
> than recomputing the 'desc_len'.  This shouldn't cause any observable
> behavior change; this way is just simpler and faster.
> 
> Signed-off-by: Eric Biggers <ebiggers@google.com>
> ---
>  security/keys/process_keys.c | 4 +---
>  1 file changed, 1 insertion(+), 3 deletions(-)
> 
> diff --git a/security/keys/process_keys.c b/security/keys/process_keys.c
> index d5b25e535d3a5..3bea09e7176d7 100644
> --- a/security/keys/process_keys.c
> +++ b/security/keys/process_keys.c
> @@ -688,9 +688,7 @@ key_ref_t lookup_user_key(key_serial_t id, unsigned long lflags,
>  		key_ref = make_key_ref(key, 0);
>  
>  		/* check to see if we possess the key */
> -		ctx.index_key.type		= key->type;
> -		ctx.index_key.description	= key->description;
> -		ctx.index_key.desc_len		= strlen(key->description);
> +		ctx.index_key			= key->index_key;
>  		ctx.match_data.raw_data		= key;
>  		kdebug("check possessed");
>  		skey_ref = search_process_keyrings(&ctx);
> -- 
> 2.19.1
> 

Ping.

             reply	other threads:[~2019-01-10 20:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-10 20:28 Eric Biggers [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-03-18 17:28 [PATCH] KEYS: reuse keyring_index_key::desc_len in lookup_user_key() Eric Biggers
2019-02-07 23:36 Eric Biggers
2018-11-03  2:10 Eric Biggers

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=20190110202837.GD149637@gmail.com \
    --to=ebiggers@kernel.org \
    --cc=keyrings@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