linux-kernel - Re: [PATCH 4/4] x86 paravirt_ops: binary patching infrastructure

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]

Date:	Mon, 07 Aug 2006 15:14:59 +1000
From:	Rusty Russell <rusty@...tcorp.com.au>
To:	Andrew Morton <akpm@...l.org>
Cc:	Andi Kleen <ak@....de>, Chris Wright <chrisw@...s-sol.org>,
	virtualization <virtualization@...ts.osdl.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 4/4] x86 paravirt_ops: binary patching infrastructure

And a trivial warning fix on that last one when !CONFIG_PARAVIRT.

struct paravirt_patch is only defined for CONFIG_PARAVIRT, so we
declare the (unused) __start and __stop section markers as char, which
causes a warning when we pass them to the dummy apply_paravirt.

Signed-off-by: Rusty Russell <rusty@...tcorp.com.au>

--- working-2.6.18-rc3-mm2/arch/i386/kernel/alternative.c.~1~	2006-08-07 14:33:13.000000000 +1000
+++ working-2.6.18-rc3-mm2/arch/i386/kernel/alternative.c	2006-08-07 15:08:21.000000000 +1000
@@ -369,7 +369,7 @@
 extern struct paravirt_patch __start_parainstructions[],
 	__stop_parainstructions[];
 #else
-void apply_paravirt(struct paravirt_patch *start, struct paravirt_patch *end)
+void apply_paravirt(void *start, void *end)
 {
 }
 extern char __start_parainstructions[], __stop_parainstructions[];


-- 
Help! Save Australia from the worst of the DMCA: http://linux.org.au/law

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