linux-kernel - [PATCH] x86,kvm: Fix section mismatches in kvm.c

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]

Date:	Thu, 2 Jul 2009 11:40:36 +0600
From:	Rakib Mullick <rakib.mullick@...il.com>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	avi@...ranet.com, LKML <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: [PATCH] x86,kvm: Fix section mismatches in kvm.c

 Impact: Fix section mismatch.

The function paravirt_ops_setup() has been refering the variable
no_timer_check, which is a __initdata. Thus generates the following
warning. paravirt_ops_setup() function is called from kvm_guest_init()
which is a __init function. So to fix this we mark paravirt_ops_setup
as __init.

Thanks,

 LD      arch/x86/built-in.o
WARNING: arch/x86/built-in.o(.text+0x166ce): Section mismatch in
reference from the function paravirt_ops_setup() to the variable
.init.data:no_timer_check
The function paravirt_ops_setup() references
the variable __initdata no_timer_check.
This is often because paravirt_ops_setup lacks a __initdata
annotation or the annotation of no_timer_check is wrong.

---
Signed-off-by: Rakib Mullick <rakib.mullick@...il.com>

--- linus/arch/x86/kernel/kvm.c	2009-07-01 20:43:56.124988432 +0600
+++ rakib/arch/x86/kernel/kvm.c	2009-07-01 20:42:38.000000000 +0600
@@ -200,7 +200,7 @@ static void kvm_leave_lazy_mmu(void)
 	state->mode = paravirt_get_lazy_mode();
 }

-static void paravirt_ops_setup(void)
+static void __init paravirt_ops_setup(void)
 {
 	pv_info.name = "KVM";
 	pv_info.paravirt_enabled = 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/