From: Christoph Hellwig <hch@infradead.org>
To: James Morris <jmorris@namei.org>
Cc: ralf@linux-mips.org, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] SELinux/MIPS: Add security hooks to mips-mt {get,set}affinity
Date: Wed, 28 Jun 2006 18:08:11 +0100 [thread overview]
Message-ID: <20060628170811.GA7162@infradead.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0606280934080.12338@d.namei>
On Wed, Jun 28, 2006 at 09:36:46AM -0400, James Morris wrote:
> From: David Quigley <dpquigl@tycho.nsa.gov>
>
> This patch adds LSM hooks into the setaffinity and getaffinity functions
> for the mips architecture to enable security modules to control these
> operations between tasks with different security attributes. This
> implementation uses the existing task_setscheduler and task_getscheduler
> LSM hooks.
I'm still watiting for an explanation how those syscalls made it in without
review, and even worse in an arch specific directory..
prev parent reply other threads:[~2006-06-28 17:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-28 13:36 James Morris
2006-06-28 16:03 ` Ralf Baechle
2006-06-28 17:08 ` Christoph Hellwig [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=20060628170811.GA7162@infradead.org \
--to=hch@infradead.org \
--cc=akpm@osdl.org \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ralf@linux-mips.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®