linux-kernel - [PATCH] security: fix description of values returned by cap_inode_need

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-next>] [day] [month] [year] [list]

Date:   Wed, 26 Jul 2017 14:31:08 -0400
From:   Stefan Berger <stefanb@...ux.vnet.ibm.com>
To:     linux-security-module@...r.kernel.org, jmorris@...ei.org
Cc:     linux-kernel@...r.kernel.org, serge@...lyn.com,
        Stefan Berger <stefanb@...ux.vnet.ibm.com>
Subject: [PATCH] security: fix description of values returned by cap_inode_need_killpriv

cap_inode_need_killpriv returns 1 if security.capability exists,
0 otherwise. Fix the description of the return value to reflect this.

Signed-off-by: Stefan Berger <stefanb@...ux.vnet.ibm.com>
---
 security/commoncap.c | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/security/commoncap.c b/security/commoncap.c
index 7abebd7..92931f8 100644
--- a/security/commoncap.c
+++ b/security/commoncap.c
@@ -302,8 +302,7 @@ static inline void bprm_clear_caps(struct linux_binprm *bprm)
  * affects the security markings on that inode, and if it is, should
  * inode_killpriv() be invoked or the change rejected?
  *
- * Returns 0 if granted; +ve if granted, but inode_killpriv() is required; and
- * -ve to deny the change.
+ * Returns 1 if security.capability has a value, 0 otherwise.
  */
 int cap_inode_need_killpriv(struct dentry *dentry)
 {
-- 
2.7.4