From: James Morris <jmorris@namei.org>
To: David Howells <dhowells@redhat.com>
Cc: Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
keyrings@linux-nfs.org, linux-kernel@vger.kernel.org
Subject: Re: [Keyrings] [PATCH 0/6] Keys: Key management updates [try #3]
Date: Tue, 20 Jun 2006 16:44:16 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0606201642050.1262@d.namei> (raw)
In-Reply-To: <20060620173735.5034.11436.stgit@warthog.cambridge.redhat.com>
On Tue, 20 Jun 2006, David Howells wrote:
> These patches update a few key management related things, mainly security
> related. They have the following prerequisite patches from Andrew Morton's -mm
> tree:
>
> selinux-add-hooks-for-key-subsystem.patch
> keys-fix-race-between-two-instantiators-of-a-key.patch
When do you think these patches will move from -mm into mainline?
I ask because I've got a bunch of SELinux patches lined up behind this
patchset, which we're aiming for 2.6.18 inclusion.
- James
--
James Morris <jmorris@namei.org>
next prev parent reply other threads:[~2006-06-20 20:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-20 17:37 David Howells
2006-06-20 17:37 ` [PATCH 1/6] Keys: Sort out key quota system " David Howells
2006-06-20 17:37 ` [PATCH 2/6] Keys: Discard the contents of a key on revocation " David Howells
2006-06-20 17:37 ` [PATCH 3/6] Keys: Let keyctl_chown() change a key's owner " David Howells
2006-06-20 17:37 ` [PATCH 4/6] Keys: Allocate key serial numbers randomly " David Howells
2006-06-20 17:37 ` [PATCH 5/6] Keys: Restrict contents of /proc/keys to Viewable keys " David Howells
2006-06-20 17:37 ` [PATCH 6/6] Keys: Add a way to store the appropriate context for newly-created " David Howells
2006-06-20 20:44 ` James Morris [this message]
2006-06-20 21:03 ` [Keyrings] [PATCH 0/6] Keys: Key management updates " Andrew Morton
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=Pine.LNX.4.64.0606201642050.1262@d.namei \
--to=jmorris@namei.org \
--cc=akpm@osdl.org \
--cc=dhowells@redhat.com \
--cc=keyrings@linux-nfs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®