From: Casey Schaufler Subject: Re: [RFC 0/28] Patches to pass vfsmount to LSM inode security hooks Date: Mon, 5 Feb 2007 11:26:39 -0800 (PST) Message-ID: <101270.11571.qm@web36602.mail.mud.yahoo.com> References: <20070205182213.12164.40927.sendpatchset@ermintrude.int.wirex.com> Reply-To: casey@schaufler-ca.com Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Cc: linux-fsdevel@vger.kernel.org, chrisw@sous-sol.org, Tony Jones , linux-security-module@vger.kernel.org, agruen@suse.de To: Tony Jones , linux-kernel@vger.kernel.org Return-path: In-Reply-To: <20070205182213.12164.40927.sendpatchset@ermintrude.int.wirex.com> Sender: linux-security-module-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org --- Tony Jones wrote: > Introduction > ------------ > > The following are a set of patches the goal of which > is to pass vfsmounts > through select portions of the VFS layer sufficient > to be visible to the LSM > inode operation hooks. > > They are being posted now as a request for comment. > Presently the AppArmor > code - being a user of the LSM interface - does not > receive the vfsmount > correspoding to an operation and has to employ > convoluted and slow mechanisms > in an attempt to determine the vfsmount which are > error prone. Would it be possible for you to describe those methods? Perhaps there is a better way to go about getting the information you need without introducing this level of change. Casey Schaufler casey@schaufler-ca.com