linux-kernel - [PATCH -next] wireless: improve airo when PROC

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]

Message-Id: <20110517123420.68f4288d.randy.dunlap@oracle.com>
Date:	Tue, 17 May 2011 12:34:20 -0700
From:	Randy Dunlap <randy.dunlap@...cle.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-wireless@...r.kernel.org
Cc:	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	linville@...driver.com
Subject: [PATCH -next] wireless: improve airo when PROC_FS is disabled

From: Randy Dunlap <randy.dunlap@...cle.com>

Skip all of the procfs-related calls when PROC_FS is not enabled.

Signed-off-by: Randy Dunlap <randy.dunlap@...cle.com>
---
 drivers/net/wireless/airo.c |    7 +++++++
 1 file changed, 7 insertions(+)

--- linux-next-20110517.orig/drivers/net/wireless/airo.c
+++ linux-next-20110517/drivers/net/wireless/airo.c
@@ -4496,6 +4496,7 @@ struct proc_data {
 	void (*on_close) (struct inode *, struct file *);
 };
 
+#ifdef CONFIG_PROC_FS
 static int setup_proc_entry( struct net_device *dev,
 			     struct airo_info *apriv ) {
 	struct proc_dir_entry *entry;
@@ -4593,6 +4594,12 @@ fail_stats_delta:
 fail:
 	return -ENOMEM;
 }
+#else
+static int setup_proc_entry( struct net_device *dev,
+			     struct airo_info *apriv ) {
+	return 0;
+}
+#endif
 
 static int takedown_proc_entry( struct net_device *dev,
 				struct airo_info *apriv ) {
--
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/