linux-kernel - [PATCH] percpu: add dummy pcpu_lpage_remapped() for !CONFIG

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: <4A5DEA0D.8050706@gmail.com>
Date:	Wed, 15 Jul 2009 23:39:09 +0900
From:	Tejun Heo <htejun@...il.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
CC:	Kamalesh Babulal <kamalesh@...ux.vnet.ibm.com>,
	linux-next@...r.kernel.org, lkml <linux-kernel@...r.kernel.org>,
	Randy Dunlap <randy.dunlap@...cle.com>
Subject: [PATCH] percpu: add dummy pcpu_lpage_remapped() for !CONFIG_SMP

!CONFIG_SMP was missing pcpu_lpage_remapped() definition causing build
failure.  Add dummy implementation.  This was discovered by linux-next
testing.

Signed-off-by: Tejun Heo <tj@...nel.org>
Cc: Randy Dunlap <randy.dunlap@...cle.com>
Cc: Kamalesh Babulal <kamalesh@...ux.vnet.ibm.com>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>
---
Yeap, it was missing dummy definition on !CONFIG_SMP.  This patch
fixes it.  Committed to percpu#for-next.  Thanks.

 include/linux/percpu.h |    5 +++++
 1 files changed, 5 insertions(+), 0 deletions(-)

diff --git a/include/linux/percpu.h b/include/linux/percpu.h
index 8ce91af..e134c82 100644
--- a/include/linux/percpu.h
+++ b/include/linux/percpu.h
@@ -184,6 +184,11 @@ static inline void free_percpu(void *p)

 static inline void __init setup_per_cpu_areas(void) { }

+static inline void *pcpu_lpage_remapped(void *kaddr)
+{
+	return NULL;
+}
+
 #endif /* CONFIG_SMP */

 #define alloc_percpu(type)	(type *)__alloc_percpu(sizeof(type), \
-- 
1.6.0.2

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