linux-kernel - Re: proxy_pda was Re: What was in the x86 merge for .20

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:	Fri, 08 Dec 2006 13:09:42 -0800
From:	Jeremy Fitzhardinge <jeremy@...p.org>
To:	Andi Kleen <ak@...e.de>
CC:	Arkadiusz Miskiewicz <arekm@...en.pl>, linux-kernel@...r.kernel.org
Subject: Re: proxy_pda was Re: What was in the x86 merge for .20

Andi Kleen wrote:
> Looking at Arkadiusz' output file it looks like gcc 4.2 decided to CSE the
> address :/
>
> 	movl	$_proxy_pda+8, %edx	#, tmp65
>
> Very sad, but legitimate.
>   

Yes, that was my conclusion too.  Though in this case the code could be
cleaned up by cutting down on the number of uses of "current" - but
that's hardly a general fix.

> The only workaround I can think of would be to define it as a symbol
> (or away in vmlinux.lds.S)

Yes.  I was thinking about setting it in vmlinux.lds to some obviously
bad address so that any access will be highly visible.

> . Or do away with the idea of proxy_pda
> again.
>   

That would be very sad indeed.

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