From: Casey Schaufler <casey@schaufler-ca.com>
To: "Serge E. Hallyn" <serue@us.ibm.com>,
lkml <linux-kernel@vger.kernel.org>,
Casey Schaufler <casey@schaufler-ca.com>,
Andrew Morgan <morgan@kernel.org>
Subject: Re: smack: use cap_task_prctl
Date: Mon, 10 Mar 2008 14:17:54 -0700 (PDT) [thread overview]
Message-ID: <785828.4605.qm@web36611.mail.mud.yahoo.com> (raw)
In-Reply-To: <20080310205456.GA13013@sergelap.austin.ibm.com>
--- "Serge E. Hallyn" <serue@us.ibm.com> wrote:
> With the introduction of per-process securebits, the capabilities-related
> prctl callbacks were moved into cap_task_prctl(). Have smack use
> cap_task_prctl() so that PR_SET_KEEPCAPS is defined.
>
> Signed-off-by: Serge E. Hallyn <serue@us.ibm.com>
Acked-by: Casey Schaufler <casey@schaufler-ca.com>
> ---
> security/smack/smack_lsm.c | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/security/smack/smack_lsm.c b/security/smack/smack_lsm.c
> index 40066b6..e8ce6b6 100644
> --- a/security/smack/smack_lsm.c
> +++ b/security/smack/smack_lsm.c
> @@ -2493,6 +2493,7 @@ static struct security_operations smack_ops = {
> .task_wait = smack_task_wait,
> .task_reparent_to_init = cap_task_reparent_to_init,
> .task_to_inode = smack_task_to_inode,
> + .task_prctl = cap_task_prctl,
>
> .ipc_permission = smack_ipc_permission,
>
> --
> 1.5.1
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
>
>
Casey Schaufler
casey@schaufler-ca.com
prev parent reply other threads:[~2008-03-10 21:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-10 20:54 smack: use cap_task_prctl Serge E. Hallyn
2008-03-10 21:17 ` Casey Schaufler [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=785828.4605.qm@web36611.mail.mud.yahoo.com \
--to=casey@schaufler-ca.com \
--cc=linux-kernel@vger.kernel.org \
--cc=morgan@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