| 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
| ||
|
Message-Id: <200612082222.33673.ak@suse.de>
Date: Fri, 8 Dec 2006 22:22:33 +0100
From: Andi Kleen <ak@...e.de>
To: Jeremy Fitzhardinge <jeremy@...p.org>
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
On Friday 08 December 2006 22:09, Jeremy Fitzhardinge wrote:
> 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.
The trouble is when it's CSEd it actually causes worse code because
a register is tied up. That might not be worth the advantage of having it?
Hmm, maybe marking it volatile would help? Arkadiusz, does the following patch
help?
-Andi
Work around gcc 4.2 CSEing the proxy_pda
proxy_pda doesn't exactly exist -- we just use it to describe side effects
of the PDA manipulation to gcc. But when gcc 4.2 CSEs the address
it generates references and worse code and the link breaks.
Let's cast it to volatile and see if it that helps.
TBD same for x86-64
Signed-off-by: Andi Kleen <ak@...e.de>
Index: linux/include/asm-i386/pda.h
===================================================================
--- linux.orig/include/asm-i386/pda.h
+++ linux/include/asm-i386/pda.h
@@ -40,19 +40,19 @@ extern struct i386_pda _proxy_pda;
switch (sizeof(_proxy_pda.field)) { \
case 1: \
asm(op "b %1,%%gs:%c2" \
- : "+m" (_proxy_pda.field) \
+ : "+m" (*(volatile T__ *)&_proxy_pda.field) \
:"ri" ((T__)val), \
"i"(pda_offset(field))); \
break; \
case 2: \
asm(op "w %1,%%gs:%c2" \
- : "+m" (_proxy_pda.field) \
+ : "+m" (*(volatile T__ *)&_proxy_pda.field) \
:"ri" ((T__)val), \
"i"(pda_offset(field))); \
break; \
case 4: \
asm(op "l %1,%%gs:%c2" \
- : "+m" (_proxy_pda.field) \
+ : "+m" (*(volatile T__ *)&_proxy_pda.field) \
:"ri" ((T__)val), \
"i"(pda_offset(field))); \
break; \
@@ -63,24 +63,25 @@ extern struct i386_pda _proxy_pda;
#define pda_from_op(op,field) \
({ \
typeof(_proxy_pda.field) ret__; \
+ typedef typeof(_proxy_pda.field) T__; \
switch (sizeof(_proxy_pda.field)) { \
case 1: \
asm(op "b %%gs:%c1,%0" \
: "=r" (ret__) \
: "i" (pda_offset(field)), \
- "m" (_proxy_pda.field)); \
+ "m" (*(volatile T__ *)&_proxy_pda.field)); \
break; \
case 2: \
asm(op "w %%gs:%c1,%0" \
: "=r" (ret__) \
: "i" (pda_offset(field)), \
- "m" (_proxy_pda.field)); \
+ "m" (*(volatile T__ *)&_proxy_pda.field)); \
break; \
case 4: \
asm(op "l %%gs:%c1,%0" \
: "=r" (ret__) \
: "i" (pda_offset(field)), \
- "m" (_proxy_pda.field)); \
+ "m" (*(volatile T__ *)&_proxy_pda.field)); \
break; \
default: __bad_pda_field(); \
} \
-
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/
Powered by blists - more mailing lists