Re: [PATCH 2/3] SELinux: add security_task_setmempolicy hooks to mmcode

[Christoph Lameter]

On Wed, 21 Jun 2006, James Morris wrote:

> I'll let David and/or Stephen address this in detail, but what's being 
> added here is a security asbtraction, where we consider these operations 
> to be equivalent from an access control point of view.  So, one task 
> causing another task's memory to be moved to another node is conisdered to 
> be "setting memory policy" at a conceptual level.  Perhaps we could change 
> the name of the hook to make that clearer (which you suggest below).

That will cause lots of confusion. Moving memory is not a memory policy.

Why was this name picked? Use move_pages movemem or so.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/