From: Andreas Gruenbacher Subject: Re: [RFD 0/4] AppArmor - Don't pass NULL nameidata to vfs_create/lookup/permission IOPs Date: Wed, 27 Jun 2007 22:42:26 +0200 Message-ID: <200706272242.26618.agruen@suse.de> References: <20070626231510.883881222@suse.de> <1182901575.12836.54.camel@heimdal.trondhjem.org> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Cc: jjohansen@suse.de, linux-kernel@vger.kernel.org, linux-security-module@vger.kernel.org, linux-fsdevel@vger.kernel.org To: Trond Myklebust Return-path: In-Reply-To: <1182901575.12836.54.camel@heimdal.trondhjem.org> Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Wednesday 27 June 2007 01:46, Trond Myklebust wrote: > On Tue, 2007-06-26 at 16:15 -0700, jjohansen@suse.de wrote: > > To remove conditionally passing of vfsmounts to the LSM, a nameidata > > struct can be instantiated in the nfsd and mqueue filesystems. This > > however results in useless information being passed down, as not > > all fields in the nameidata struct will be meaingful. The nameidata > > struct is split creating struct nameidata2 that contains only the > > fields > > that will carry meaningful information. > > I don't object to the concept per se, but could you please give it a > more descriptive name please? "struct vfs_intent" would be a lot more > accurate than "nameidata2". Yes, the name is pretty arbitrary. vfs_intent is better, even though the struct doesn't only include the intent data. Thanks, Andreas