From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750990AbWFUUrT (ORCPT ); Wed, 21 Jun 2006 16:47:19 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750995AbWFUUrT (ORCPT ); Wed, 21 Jun 2006 16:47:19 -0400 Received: from mail3.sea5.speakeasy.net ([69.17.117.5]:27608 "EHLO mail3.sea5.speakeasy.net") by vger.kernel.org with ESMTP id S1750864AbWFUUrS (ORCPT ); Wed, 21 Jun 2006 16:47:18 -0400 Date: Wed, 21 Jun 2006 16:47:15 -0400 (EDT) From: James Morris X-X-Sender: jmorris@d.namei To: Christoph Lameter cc: Andrew Morton , linux-kernel@vger.kernel.org, Stephen Smalley , Eric Paris , David Quigley , Chris Wright Subject: Re: [PATCH 2/3] SELinux: add security_task_setmempolicy hooks to mm code In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 21 Jun 2006, Christoph Lameter wrote: > 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. Not sure, perhaps some earlier thinking that stuck around. Thanks for looking at it, I'll respin the patches. -- James Morris