linux-kernel - Re: [PATCH] x86-64: re-use kernel/syscall_table

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] [day] [month] [year] [list]

Message-ID: <4DB9AF3C.3090901@zytor.com>
Date:	Thu, 28 Apr 2011 11:17:32 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Arnd Bergmann <arnd@...db.de>
CC:	Jan Beulich <JBeulich@...ell.com>, mingo@...e.hu,
	tglx@...utronix.de, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86-64: re-use kernel/syscall_table_32.S in ia32/ia32entry.S

On 04/28/2011 05:35 AM, Arnd Bergmann wrote:
>>
>> Yep, something like that (although I have to say the __SC_3264 syntax
>> makes me want to barf.)
> 
> If you have a suggestion for a better syntax, I'd hope we can do
> that in asm-generic as well. My goal is to have those files set
> an example of how to best write architecture specific versions if
> they have to be different.
> 

I would just call it __SYSCALL2() -- for two versions of this syscall.
I'm not all that fond of our current "compat" notion hard-coding the
assumption of a "primary" and a "compat" ABI -- largely because that
assumption is frequently false, and it is a clear violation of the
zero-one-infinity rule.

	-hpa

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