linux-kernel - [PATCH 2/4] capability: security/capability.c whitespace, syntax, and other cleanups

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:	Wed, 23 Apr 2008 13:52:32 -0400
From:	eparis@...hat.com
To:	linux-kernel@...r.kernel.org
Cc:	jmorris@...ei.org, serue@...ibm.com, Eric Paris <eparis@...hat.com>
Subject: [PATCH 2/4] capability: security/capability.c whitespace, syntax, and other cleanups

From: Eric Paris <eparis@...hat.com>

This patch changes security/capability.c to fix whitespace and syntax issues.  Things that
are fixed may include (does not not have to include)

whitespace at end of lines
spaces followed by tabs
spaces used instead of tabs
spacing around parenthesis
location of { around structs and else clauses
location of * in pointer declarations
removal of initialization of static data to keep it in the right section
useless {} in if statemetns
useless checking for NULL before kfree
fixing of the indentation depth of switch statements
no assignments in if statements
include spaces around , in function calls
and any number of other things I forgot to mention

Signed-off-by: Eric Paris <eparis@...hat.com>
---
 security/capability.c |   20 ++++++++++----------
 1 files changed, 10 insertions(+), 10 deletions(-)

diff --git a/security/capability.c b/security/capability.c
index 2c6e06d..e77d5e4 100644
--- a/security/capability.c
+++ b/security/capability.c
@@ -46,9 +46,9 @@ static struct security_operations capability_ops = {
 	.task_post_setuid =		cap_task_post_setuid,
 	.task_reparent_to_init =	cap_task_reparent_to_init,
 
-	.syslog =                       cap_syslog,
+	.syslog =			cap_syslog,
 
-	.vm_enough_memory =             cap_vm_enough_memory,
+	.vm_enough_memory =		cap_vm_enough_memory,
 };
 
 /* flag to keep track of how we were registered */
@@ -57,25 +57,25 @@ static int secondary;
 static int capability_disable;
 module_param_named(disable, capability_disable, int, 0);
 
-static int __init capability_init (void)
+static int __init capability_init(void)
 {
 	if (capability_disable) {
 		printk(KERN_INFO "Capabilities disabled at initialization\n");
 		return 0;
 	}
 	/* register ourselves with the security framework */
-	if (register_security (&capability_ops)) {
+	if (register_security(&capability_ops)) {
 		/* try registering with primary module */
-		if (mod_reg_security (KBUILD_MODNAME, &capability_ops)) {
-			printk (KERN_INFO "Failure registering capabilities "
-				"with primary security module.\n");
+		if (mod_reg_security(KBUILD_MODNAME, &capability_ops)) {
+			printk(KERN_INFO "Failure registering capabilities "
+			       "with primary security module.\n");
 			return -EINVAL;
 		}
 		secondary = 1;
 	}
-	printk (KERN_INFO "Capability LSM initialized%s\n",
-		secondary ? " as secondary" : "");
+	printk(KERN_INFO "Capability LSM initialized%s\n",
+	       secondary ? " as secondary" : "");
 	return 0;
 }
 
-security_initcall (capability_init);
+security_initcall(capability_init);
-- 
1.5.2.1

--
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/