linux-kernel - [patch] x86, xen, vdso: fix build error, add sysctl

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]

Message-ID: <20080711203435.GA29286@elte.hu>
Date:	Fri, 11 Jul 2008 22:34:35 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	linux-kernel@...r.kernel.org, Jeremy Fitzhardinge <jeremy@...p.org>
Subject: [patch] x86, xen, vdso: fix build error, add sysctl_vsyscall32

commit c187263834465c2beededb4d19e7f6bab18cc757
Author: Ingo Molnar <mingo@...e.hu>
Date:   Fri Jul 11 22:34:26 2008 +0200

    x86, xen, vdso: fix build error, add sysctl_vsyscall32
    
    Xen recently tried to make use of sysctl_vsyscall32, with this result:
    
     arch/x86/xen/built-in.o: In function `xen_enable_syscall':
     (.cpuinit.text+0xdb): undefined reference to `sysctl_vsyscall32'
    
    turns out when sysctl_vsyscall32 use was introduced, the variable
    was not defined anywhere.
    
    Signed-off-by: Ingo Molnar <mingo@...e.hu>
---
 arch/x86/vdso/vdso32-setup.c |    2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)

diff --git a/arch/x86/vdso/vdso32-setup.c b/arch/x86/vdso/vdso32-setup.c
index 0bce542..0645fe9 100644
--- a/arch/x86/vdso/vdso32-setup.c
+++ b/arch/x86/vdso/vdso32-setup.c
@@ -377,6 +377,8 @@ __initcall(sysenter_setup);
 /* Register vsyscall32 into the ABI table */
 #include <linux/sysctl.h>
 
+int sysctl_vsyscall32;
+
 static ctl_table abi_table2[] = {
 	{
 		.procname	= "vsyscall32",
--
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/