[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <124ae3859e8141deb35ed8355370b4ed@AcuMS.aculab.com>
Date: Thu, 20 Sep 2018 08:51:09 +0000
From: David Laight <David.Laight@...LAB.COM>
To: 'Casey Schaufler' <casey@...aufler-ca.com>,
LSM <linux-security-module@...r.kernel.org>,
James Morris <jmorris@...ei.org>,
"SE Linux" <selinux@...ho.nsa.gov>,
LKLM <linux-kernel@...r.kernel.org>,
"John Johansen" <john.johansen@...onical.com>,
Kees Cook <keescook@...omium.org>,
Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>,
Paul Moore <paul@...l-moore.com>,
Stephen Smalley <sds@...ho.nsa.gov>,
"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
"Alexey Dobriyan" <adobriyan@...il.com>,
Mickaël Salaün <mic@...ikod.net>,
Salvatore Mesoraca <s.mesoraca16@...il.com>
Subject: RE: [PATCH v3 09/16] SELinux: Abstract use of file security blob
From: Casey Schaufler
> Sent: 20 September 2018 01:21
>
> SELinux: Abstract use of file security blob
>
> Don't use the file->f_security pointer directly.
> Provide a helper function that provides the security blob pointer.
...
> +static inline struct file_security_struct *selinux_file(const struct file *file)
> +{
> + return file->f_security;
> +}
> +
Why?
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
Powered by blists - more mailing lists