Messages in this thread | | | Date | Thu, 22 Jun 2006 07:31:02 -0500 | From | "Serge E. Hallyn" <> | Subject | Re: [PATCH 2/3] SELinux: add security_task_movememory calls to mm code |
| |
Quoting James Morris (jmorris@namei.org): > From: David Quigley <dpquigl@tycho.nsa.gov> > > This patch inserts security_task_movememory hook calls into memory > management code to enable security modules to mediate this operation > between tasks. > > Since the last posting, the hook has been renamed following feedback from > Christoph Lameter. > > This patch is aimed at 2.6.18 inclusion. > > Please apply.
Hi,
sorry if I'm being dense - what is actually being protected against here? The only thing I can think of is one process causing performance degradation to another by moving it's memory further from it's cpu on a NUMA machine.
Is there something more? (And is what I'm guessing even possible?)
I'm not arguing against this hook, just wondering whether there's more to this than I see.
thanks, -serge - 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/
| |