linux-kernel - [PATCH] x86: reduce forbid

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <4880AC40.76E4.0078.0@novell.com>
Date:	Fri, 18 Jul 2008 13:44:16 +0100
From:	"Jan Beulich" <jbeulich@...ell.com>
To:	<mingo@...e.hu>, <tglx@...utronix.de>, <hpa@...or.com>
Cc:	<linux-kernel@...r.kernel.org>
Subject: [PATCH] x86: reduce forbid_dac's visibility

It's not used anywhere outside its declaring file.

Signed-off-by: Jan Beulich <jbeulich@...ell.com>

---
 arch/x86/kernel/pci-dma.c     |    3 +--
 include/asm-x86/dma-mapping.h |    1 -
 2 files changed, 1 insertion(+), 3 deletions(-)

--- linux-2.6.26/arch/x86/kernel/pci-dma.c	2008-07-13 23:51:29.000000000 +0200
+++ 2.6.26-x86-forbid-dac/arch/x86/kernel/pci-dma.c	2008-07-15 14:51:28.000000000 +0200
@@ -8,8 +8,7 @@
 #include <asm/gart.h>
 #include <asm/calgary.h>
 
-int forbid_dac __read_mostly;
-EXPORT_SYMBOL(forbid_dac);
+static int forbid_dac __read_mostly;
 
 const struct dma_mapping_ops *dma_ops;
 EXPORT_SYMBOL(dma_ops);
--- linux-2.6.26/include/asm-x86/dma-mapping.h	2008-07-13 23:51:29.000000000 +0200
+++ 2.6.26-x86-forbid-dac/include/asm-x86/dma-mapping.h	2008-07-17 10:29:09.000000000 +0200
@@ -14,7 +14,6 @@ extern dma_addr_t bad_dma_address;
 extern int iommu_merge;
 extern struct device fallback_dev;
 extern int panic_on_overflow;
-extern int forbid_dac;
 extern int force_iommu;
 
 struct dma_mapping_ops {



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