linux-kernel - Re: [PATCH] paravirt reorder functions to avoid unspecified behaviour

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: <p73mz6ddtx4.fsf@bingen.suse.de>
Date:	27 Nov 2006 12:13:11 +0100
From:	Andi Kleen <ak@...e.de>
To:	Andy Whitcroft <apw@...dowen.org>
Cc:	Rusty Russell <rusty@...tcorp.com.au>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] paravirt reorder functions to avoid unspecified behaviour

Andy Whitcroft <apw@...dowen.org> writes:

> paravirt: reorder functions to avoid unspecified behaviour
> 
> The paravirt ops introduce a 'weak' attribute onto memory_setup().
> Code ordering leads to the following warnings on x86:
> 
>     arch/i386/kernel/setup.c:651: warning: weak declaration of
> 		`memory_setup' after first use results in unspecified behavior
> 
> Move memory_setup() to avoid this.

I added the patch to the original patch thanks

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