From: Paul Jackson <pj@sgi.com>
To: James Morris <jmorris@namei.org>
Cc: akpm@osdl.org, sds@tycho.nsa.gov, linux-kernel@vger.kernel.org,
dpquigl@tycho.nsa.gov, mingo@elte.hu
Subject: Re: [PATCH 2/2] SELinux: Add security hook call to mediate attach_task (kernel/cpuset.c)
Date: Tue, 20 Jun 2006 23:40:13 -0700 [thread overview]
Message-ID: <20060620234013.2d3c07d7.pj@sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0606210029230.5379@d.namei>
James wrote:
> This patch adds a security hook call to enable security modules to control
> the ability to attach a task to a cpuset.
Looks reasonable to me. Thanks.
Acked-by: Paul Jackson <pj@sgi.com>
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.925.600.0401
prev parent reply other threads:[~2006-06-21 6:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-21 4:29 [PATCH 1/2] SELinux: Add security hooks to {get,set}affinity James Morris
2006-06-21 4:32 ` [PATCH 2/2] SELinux: Add security hook call to mediate attach_task (kernel/cpuset.c) James Morris
2006-06-21 6:40 ` Paul Jackson [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=20060620234013.2d3c07d7.pj@sgi.com \
--to=pj@sgi.com \
--cc=akpm@osdl.org \
--cc=dpquigl@tycho.nsa.gov \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sds@tycho.nsa.gov \
/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