From: David Howells <dhowells@redhat.com>
To: James Morris <jmorris@namei.org>
Cc: dhowells@redhat.com, David Chinner <dgc@sgi.com>,
lkml <linux-kernel@vger.kernel.org>,
linux-security-module@vger.kernel.org,
Eric Paris <eparis@redhat.com>
Subject: Re: [patch, rfc] mm.h, security.h, key.h and preventing namespace poisoning
Date: Wed, 02 Jan 2008 15:41:06 +0000 [thread overview]
Message-ID: <32216.1199288466@redhat.com> (raw)
In-Reply-To: <Xine.LNX.4.64.0712201506520.6851@us.intercode.com.au>
James Morris <jmorris@namei.org> wrote:
> I suspect it may be useful ensure all global identifiers for the key
> subsystem are prefixed with key_, as 'copy_keys' does seem a little
> generic.
Many of the fork helpers are called copy_xxx().
David
next prev parent reply other threads:[~2008-01-02 15:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-19 9:38 [patch, rfc] mm.h, security.h, key.h and preventing namespace poisoning David Chinner
2007-12-19 10:15 ` Alexey Dobriyan
2007-12-20 0:07 ` James Morris
2007-12-20 1:44 ` David Chinner
2007-12-20 4:11 ` James Morris
2007-12-25 22:05 ` Andrew Morton
2007-12-26 4:15 ` James Morris
2008-01-02 15:41 ` David Howells [this message]
2007-12-20 18:08 ` Eric Paris
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=32216.1199288466@redhat.com \
--to=dhowells@redhat.com \
--cc=dgc@sgi.com \
--cc=eparis@redhat.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@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 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.