From: Andrew Morgan <morgan@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Linux Security Modules List
<linux-security-module@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>,
"Serge E. Hallyn" <serue@us.ibm.com>,
James Morris <jmorris@namei.org>
Subject: Re: [PATCH] capabilities: implement per-process securebits
Date: Sun, 27 Apr 2008 14:26:12 -0700 [thread overview]
Message-ID: <4814EF74.4050508@kernel.org> (raw)
In-Reply-To: <20080426081810.7f1245e7.akpm@linux-foundation.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
OK. Thanks.
Cheers
Andrew
Andrew Morton wrote:
| On Mon, 18 Feb 2008 18:25:37 -0800 "Andrew G. Morgan"
<morgan@kernel.org> wrote:
|
|> Here is the patch to add per-process securebits again. This version
|> includes Serge's argument type fix (thanks), but is otherwise unchanged
|> from the one posted a couple of weeks back. It is against Linus' tree as
|> of a the 15th.
|
| The hitherto-invisible-to-me PR_GET_TSC and PR_SET_TSC have turned up in
| mainline, so I have renumbered your prctl options to
|
| /* Get/set securebits (as per security/commoncap.c) */
| #define PR_GET_SECUREBITS 27
| #define PR_SET_SECUREBITS 28
|
| --
| To unsubscribe from this list: send the line "unsubscribe
linux-security-module" in
| the body of a message to majordomo@vger.kernel.org
| More majordomo info at http://vger.kernel.org/majordomo-info.html
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFIFO9x+bHCR3gb8jsRAqgmAJ4zd97eTDcB0r9ipPvli23KYFuEmACgmSzu
x0njikL5e+gf6//Raac3qY0=
=xc7N
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2008-04-27 21:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-19 2:25 [PATCH] capabilities: implement per-process securebits Andrew G. Morgan
2008-02-20 17:42 ` Serge E. Hallyn
2008-02-22 1:59 ` Andrew G. Morgan
2008-02-22 6:11 ` Andrew G. Morgan
2008-02-22 16:22 ` Serge E. Hallyn
2008-04-26 15:18 ` Andrew Morton
2008-04-27 21:26 ` Andrew Morgan [this message]
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=4814EF74.4050508@kernel.org \
--to=morgan@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=serue@us.ibm.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