Messages in this thread | | | 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 |
| |
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 - 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/
| |