linux-kernel - Re: [RFC 0/28] Patches to pass vfsmount to LSM inode security hooks

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]

Date:	Mon, 5 Feb 2007 18:30:43 -0800
From:	Andreas Gruenbacher <agruen@...e.de>
To:	Chris Wright <chrisw@...s-sol.org>
Cc:	Casey Schaufler <casey@...aufler-ca.com>,
	Tony Jones <tonyj@...e.de>, linux-kernel@...r.kernel.org,
	linux-fsdevel@...r.kernel.org,
	linux-security-module@...r.kernel.org
Subject: Re: [RFC 0/28] Patches to pass vfsmount to LSM inode security hooks

On Monday 05 February 2007 11:50, Chris Wright wrote:
> This kind of change (or perhaps straight to struct path) is definitely
> needed from AA. 

I tried struct path; in terms of code size it doesn't seem worth it. We could 
get identical code out of it as if we were passing the dentry and vfsmount 
individually, with somewhat slimmer looking interfaces, but then we'd have to 
create temporary struct path objects in a few places, and accessing either 
object would become a bit more verbose (path.dentry instead of dentry, etc.)

See the following thread on linux-kernel, Message-ID 
200702031425.38054.agruen@...e.de:

  [RFC] Pack the vfsmount and dentry in nameidata into a struct path

Thanks,
Andreas
-
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/