linux-kernel - Re: [patch 09/14] security: dont pass nameidata to security_inode

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Xine.LNX.4.64.0805220852020.8393@us.intercode.com.au>
Date:	Thu, 22 May 2008 08:52:22 +1000 (EST)
From:	James Morris <jmorris@...ei.org>
To:	Miklos Szeredi <miklos@...redi.hu>
cc:	linux-fsdevel@...r.kernel.org, hch@...radead.org,
	viro@...IV.linux.org.uk, linux-kernel@...r.kernel.org,
	Stephen Smalley <sds@...ho.nsa.gov>,
	Eric Paris <eparis@...hat.com>,
	Casey Schaufler <casey@...aufler-ca.com>
Subject: Re: [patch 09/14] security: dont pass nameidata to security_inode_permission()

On Wed, 21 May 2008, Miklos Szeredi wrote:

> From: Miklos Szeredi <mszeredi@...e.cz>
> 
> Only pass nameidata->flags instead of the nameidata to
> security_inode_permission(), synchronizing it with i_op->permission().
> 
> Currently no security module uses the nameidata parameter.
> 
> The other change in ->permission() is that a dentry is passed instead
> of an inode.  Leave this till AppArmor integration, since that will
> need a struct path instead of an inode.
> 
> Signed-off-by: Miklos Szeredi <mszeredi@...e.cz>
> CC: James Morris <jmorris@...ei.org>
> CC: Stephen Smalley <sds@...ho.nsa.gov>
> CC: Eric Paris <eparis@...hat.com>
> CC: Casey Schaufler <casey@...aufler-ca.com>

Acked-by: James Morris <jmorris@...ei.org>



-- 
James Morris
<jmorris@...ei.org>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/