From: David Howells <dhowells@redhat.com> Cc: dhowells@redhat.com, ebiederm@xmission.com, keyrings@vger.kernel.org, linux-cifs@vger.kernel.org, linux-nfs@vger.kernel.org, netdev@vger.kernel.org, linux-afs@lists.infradead.org, dwalsh@redhat.com, vgoyal@redhat.com, linux-security-module@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 0/9] keys: Namespacing [ver #4] Date: Wed, 19 Jun 2019 16:09:26 +0000 [thread overview] Message-ID: <10072.1560960566@warthog.procyon.org.uk> (raw) In-Reply-To: <156096036064.6697.2432500504898119675.stgit@warthog.procyon.org.uk> Apologies... A couple of the patches don't compile because I forgot to commit a change:-( Will repush and repost. David
WARNING: multiple messages have this Message-ID (diff)
From: David Howells <dhowells@redhat.com> To: unlisted-recipients:; (no To-header on input) Cc: dhowells@redhat.com, ebiederm@xmission.com, keyrings@vger.kernel.org, linux-cifs@vger.kernel.org, linux-nfs@vger.kernel.org, netdev@vger.kernel.org, linux-afs@lists.infradead.org, dwalsh@redhat.com, vgoyal@redhat.com, linux-security-module@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 0/9] keys: Namespacing [ver #4] Date: Wed, 19 Jun 2019 17:09:26 +0100 [thread overview] Message-ID: <10072.1560960566@warthog.procyon.org.uk> (raw) In-Reply-To: <156096036064.6697.2432500504898119675.stgit@warthog.procyon.org.uk> Apologies... A couple of the patches don't compile because I forgot to commit a change:-( Will repush and repost. David
next prev parent reply other threads:[~2019-06-19 16:09 UTC|newest] Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-06-19 16:06 [PATCH 0/9] keys: Namespacing [ver #4] David Howells 2019-06-19 16:06 ` David Howells 2019-06-19 16:06 ` [PATCH 1/9] keys: Simplify key description management " David Howells 2019-06-19 16:06 ` David Howells 2019-06-19 16:06 ` [PATCH 2/9] keys: Cache the hash value to avoid lots of recalculation " David Howells 2019-06-19 16:06 ` David Howells 2019-06-19 16:06 ` [PATCH 3/9] keys: Add a 'recurse' flag for keyring searches " David Howells 2019-06-19 16:06 ` David Howells 2019-06-19 16:06 ` [PATCH 4/9] keys: Namespace keyring names " David Howells 2019-06-19 16:06 ` David Howells 2019-06-19 16:06 ` [PATCH 5/9] keys: Move the user and user-session keyrings to the user_namespace " David Howells 2019-06-19 16:06 ` David Howells 2019-06-19 16:09 ` David Howells [this message] 2019-06-19 16:09 ` [PATCH 0/9] keys: Namespacing " David Howells 2019-06-19 16:46 ` David Howells 2019-06-19 16:46 ` David Howells 2019-06-19 16:46 ` [PATCH 1/9] keys: Simplify key description management " David Howells 2019-06-19 16:46 ` David Howells 2019-06-19 16:46 ` [PATCH 2/9] keys: Cache the hash value to avoid lots of recalculation " David Howells 2019-06-19 16:46 ` David Howells 2019-06-19 16:47 ` [PATCH 3/9] keys: Add a 'recurse' flag for keyring searches " David Howells 2019-06-19 16:47 ` David Howells 2019-06-19 16:47 ` [PATCH 4/9] keys: Namespace keyring names " David Howells 2019-06-19 16:47 ` David Howells 2019-06-19 16:47 ` [PATCH 5/9] keys: Move the user and user-session keyrings to the user_namespace " David Howells 2019-06-19 16:47 ` David Howells 2019-06-19 16:47 ` [PATCH 6/9] keys: Include target namespace in match criteria " David Howells 2019-06-19 16:47 ` David Howells 2019-06-19 16:47 ` [PATCH 7/9] keys: Garbage collect keys for which the domain has been removed " David Howells 2019-06-19 16:47 ` David Howells 2019-06-19 16:47 ` [PATCH 8/9] keys: Network namespace domain tag " David Howells 2019-06-19 16:47 ` David Howells 2019-06-27 20:55 ` Willem de Bruijn 2019-06-27 20:55 ` Willem de Bruijn 2019-06-27 22:07 ` David Howells 2019-06-27 22:07 ` David Howells 2019-06-19 16:48 ` [PATCH 9/9] keys: Pass the network namespace into request_key mechanism " David Howells 2019-06-19 16:48 ` 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=10072.1560960566@warthog.procyon.org.uk \ --to=dhowells@redhat.com \ --cc=dwalsh@redhat.com \ --cc=ebiederm@xmission.com \ --cc=keyrings@vger.kernel.org \ --cc=linux-afs@lists.infradead.org \ --cc=linux-cifs@vger.kernel.org \ --cc=linux-fsdevel@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-nfs@vger.kernel.org \ --cc=linux-security-module@vger.kernel.org \ --cc=netdev@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: linkBe 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.