[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <163c782b51c696ea210dfa9043ea64cabac44ef7.1549540487.git.efremov@ispras.ru>
Date: Thu, 7 Feb 2019 15:44:49 +0300
From: Denis Efremov <efremov@...ras.ru>
To: Eric Paris <eparis@...isplace.org>
Cc: Denis Efremov <efremov@...ras.ru>,
Casey Schaufler <casey@...aufler-ca.com>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
Kees Cook <keescook@...omium.org>,
John Johansen <john.johansen@...onical.com>,
James Morris <jmorris@...ei.org>,
"Serge E. Hallyn" <serge@...lyn.com>,
Paul Moore <paul@...l-moore.com>,
Kentaro Takeda <takedakn@...data.co.jp>,
linux-security-module@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: [PATCH 01/10] security: fix documentation for the sb_copy_data hook
The @type argument of the sb_copy_data hook was removed
in the commit "LSM/SELinux: Interfaces to allow FS to control
mount options" (e0007529893c). This commit removes the description
of the @type argument from the LSM documentation.
Signed-off-by: Denis Efremov <efremov@...ras.ru>
---
include/linux/lsm_hooks.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/include/linux/lsm_hooks.h b/include/linux/lsm_hooks.h
index 9a0bdf91e646..de179331be5c 100644
--- a/include/linux/lsm_hooks.h
+++ b/include/linux/lsm_hooks.h
@@ -111,7 +111,6 @@
* options cleanly (a filesystem may modify the data e.g. with strsep()).
* This also allows the original mount data to be stripped of security-
* specific options to avoid having to make filesystems aware of them.
- * @type the type of filesystem being mounted.
* @orig the original mount data copied from userspace.
* @copy copied data which will be passed to the security module.
* Returns 0 if the copy was successful.
--
2.17.2
Powered by blists - more mailing lists