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, 03 Aug 2009 10:01:19 +0900
From:	Tejun Heo <tj@...nel.org>
To:	"H. Peter Anvin" <hpa@...or.com>
CC:	Paul Mackerras <paulus@...ba.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Ingo Molnar <mingo@...e.hu>,
	Thomas Gleixner <tglx@...utronix.de>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] Additional x86 fixes for 2.6.31-rc5

Hello,

H. Peter Anvin wrote:
> You can't actually do "lea %gs:foo,%rbx" (lea doesn't include the
> segment offset, unfortunately; I asked AMD to change that on 64 bits
> but, not too surprisingly, they weren't able to make that change.)
> Getting the address is expensive, but it's obviously possible -- which
> may have similar bad results.  It would be worth experimenting with a
> little bit, though.

Yeap, this part is strange.  I can't understand why it was done that
way.  Interestingly, the segment override doesn't trigger any
exception, it just gets ignored.  Is there a way to retrieve %gs value
without accessing memory?  ie. other than %gs:identity_gs?

Thanks.

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

Powered by Openwall GNU/*/Linux Powered by OpenVZ