From: David Howells <dhowells@redhat.com>
To: Andrew Zaborowski <andrew.zaborowski@intel.com>
Cc: dhowells@redhat.com, ebiederm@xmission.com,
keyrings@vger.kernel.org, linux-security-module@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
dwalsh@redhat.com, vgoyal@redhat.com
Subject: Re: [PATCH 05/11] keys: Add a 'recurse' flag for keyring searches
Date: Thu, 25 Apr 2019 12:02:42 +0100 [thread overview]
Message-ID: <20948.1556190162@warthog.procyon.org.uk> (raw)
In-Reply-To: <CAOq732KsRiXtGD9Wj-iGB77pqJbprCiuDKy_Ypi=dLfvn_9QNQ@mail.gmail.com>
Andrew Zaborowski <andrew.zaborowski@intel.com> wrote:
> > extern key_ref_t keyring_search(key_ref_t keyring,
> > struct key_type *type,
> > - const char *description);
> > + const char *description,
> > + bool no_recurse);
>
> No functional difference but it's "recurse" everywhere else.
Fixed, thanks.
David
next prev parent reply other threads:[~2019-04-25 11:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-24 16:13 [PATCH 00/11] keys: Namespacing David Howells
2019-04-24 16:13 ` [PATCH 01/11] keys: Invalidate used request_key authentication keys David Howells
2019-04-24 16:13 ` [PATCH 02/11] keys: Kill off request_key_async{,_with_auxdata} David Howells
2019-04-24 16:13 ` [PATCH 03/11] keys: Simplify key description management David Howells
2019-04-24 16:14 ` [PATCH 04/11] keys: Cache the hash value to avoid lots of recalculation David Howells
2019-04-24 16:14 ` [PATCH 05/11] keys: Add a 'recurse' flag for keyring searches David Howells
2019-04-25 4:27 ` Andrew Zaborowski
2019-04-25 11:02 ` David Howells [this message]
2019-04-24 16:14 ` [PATCH 06/11] keys: Namespace keyring names David Howells
2019-04-24 16:14 ` [PATCH 07/11] keys: Move the user and user-session keyrings to the user_namespace David Howells
2019-04-24 22:03 ` Jann Horn
2019-04-24 22:24 ` David Howells
2019-04-25 11:38 ` David Howells
2019-04-24 16:14 ` [PATCH 08/11] keys: Include target namespace in match criteria David Howells
2019-04-24 16:14 ` [PATCH 09/11] keys: Garbage collect keys for which the domain has been removed David Howells
2019-04-24 16:14 ` [PATCH 10/11] keys: Network namespace domain tag David Howells
2019-04-24 21:54 ` David Howells
2019-04-24 16:15 ` [PATCH 11/11] keys: Pass the network namespace into request_key mechanism David Howells
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=20948.1556190162@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=andrew.zaborowski@intel.com \
--cc=dwalsh@redhat.com \
--cc=ebiederm@xmission.com \
--cc=keyrings@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=vgoyal@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