linux-kernel - Re: [PATCH] x86/entry: Improve system call entry comments

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: <56DF1C98.6030506@zytor.com>
Date:	Tue, 8 Mar 2016 10:40:24 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Ingo Molnar <mingo@...nel.org>
Cc:	Andy Lutomirski <luto@...nel.org>, x86@...nel.org,
	linux-kernel@...r.kernel.org, Borislav Petkov <bp@...en8.de>,
	Oleg Nesterov <oleg@...hat.com>,
	Andrew Cooper <andrew.cooper3@...rix.com>,
	Brian Gerst <brgerst@...il.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH] x86/entry: Improve system call entry comments

On 03/08/16 02:30, Ingo Molnar wrote:
>>>> + *
>>>> + * This is considered a slow path.  It is not used by modern libc
>>>> + * implementations on modern hardware except during process startup.
>>>> + *
>>
>> Sadly I believe Android still uses int $0x80 in the upstream version.
> 
> I don't see how that fact conflicts with my statement: on 64-bit kernels INT $0x80 
> will (of course) work, but will land on another entry point: entry_INT80_compat(), 
> not entry_INT80_32().
> 
> On 32-bit kernels the INT $0x80 entry point is entry_INT80_32().
> 

It doesn't.  I was referring to the above quote. Trying to fix that.

	-hpa