From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [patch 01/15] security: pass path to inode_create Date: Sat, 31 May 2008 04:30:52 -0400 Message-ID: <20080531083052.GH24135@infradead.org> References: <20080529134903.615127628@szeredi.hu> <20080529134958.655985182@szeredi.hu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: linux-security-module@vger.kernel.org, linux-fsdevel@vger.kernel.org, jmorris@namei.org, sds@tycho.nsa.gov, eparis@redhat.com, casey@schaufler-ca.com, agruen@suse.de, jjohansen@suse.de, penguin-kernel@I-love.SAKURA.ne.jp, hch@infradead.org, viro@ZenIV.linux.org.uk, linux-kernel@vger.kernel.org To: Miklos Szeredi Return-path: Content-Disposition: inline In-Reply-To: <20080529134958.655985182@szeredi.hu> Sender: linux-security-module-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Thu, May 29, 2008 at 03:49:04PM +0200, Miklos Szeredi wrote: > From: Miklos Szeredi > > In the inode_create() security operation and related functions pass > the path (vfsmount + dentry) to the parent directory instead of the > inode. AppArmor will need this. So you're once again switching vfs_ to a pass a vfsmount argument, this time hidden under struct path. It's really hard to grasp a "no" sometimes, isn't it? :)