Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 27 Feb 2018 00:57:21 +0000
From: Al Viro <>
To: Mickaël Salaün <>
Cc:, Alexei Starovoitov <>,
	Andy Lutomirski <>,
	Arnaldo Carvalho de Melo <>,
	Casey Schaufler <>,
	Daniel Borkmann <>,
	David Drysdale <>,
	"David S . Miller" <>,
	"Eric W . Biederman" <>,
	James Morris <>,
	Jann Horn <>, Jonathan Corbet <>,
	Michael Kerrisk <>,
	Kees Cook <>, Paul Moore <>,
	Sargun Dhillon <>,
	"Serge E . Hallyn" <>,
	Shuah Khan <>, Tejun Heo <>,
	Thomas Graf <>, Tycho Andersen <>,
	Will Drewry <>,,,,, James Morris <>,
	John Johansen <>,
	Stephen Smalley <>,
	Tetsuo Handa <>,
Subject: Re: [PATCH bpf-next v8 01/11] fs,security: Add a security blob to

On Tue, Feb 27, 2018 at 01:41:11AM +0100, Mickaël Salaün wrote:
> The function current_nameidata_security(struct inode *) can be used to
> retrieve a blob's pointer address tied to the inode being walk through.
> This enable to follow a path lookup and know where an inode access come
> from. This is needed for the Landlock LSM to be able to restrict access
> to file path.
> The LSM hook nameidata_free_security(struct inode *) is called before
> freeing the associated nameidata.

NAK.  Not without well-defined semantics and "some Linux S&M uses that for
something, don't ask what" does not count.

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.