linux-kernel - Re: [PATCH 1/3] x86_64: further cleanup of 32-bit compat syscall mechanisms

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: <487BCC25.9030204@goop.org>
Date:	Mon, 14 Jul 2008 14:59:01 -0700
From:	Jeremy Fitzhardinge <jeremy@...p.org>
To:	"H. Peter Anvin" <hpa@...nel.org>
CC:	Ingo Molnar <mingo@...e.hu>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	the arch/x86 maintainers <x86@...nel.org>
Subject: Re: [PATCH 1/3] x86_64: further cleanup of 32-bit compat syscall
 mechanisms

H. Peter Anvin wrote:
> Jeremy Fitzhardinge wrote:
>> AMD only supports "syscall" from 32-bit compat usermode.
>> Intel and Centaur(?) only support "sysenter" from 32-bit compat 
>> usermode.
>>
>> Set the X86 feature bits accordingly, and set up the vdso in
>> accordance with those bits.  On the offchance we run on in a 64-bit
>> environment which supports neither syscall nor sysenter from 32-bit
>> mode, then fall back to the int $0x80 vdso.
>>
>> Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@...rix.com>
>
> Acked-by: H. Peter Anvin <hpa@...or.com> 

Have these been applied to anything yet?

    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/