linux-kernel - Re: [PATCH] x86: Wire up 32-bit direct socket calls

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:	Wed, 02 Sep 2015 13:16:19 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Geert Uytterhoeven <geert@...ux-m68k.org>,
	Andy Lutomirski <luto@...nel.org>
CC:	X86 ML <x86@...nel.org>,
	Network Development <netdev@...r.kernel.org>,
	Tulio Magno Quites Machado Filho 
	<tuliom@...ux.vnet.ibm.com>, Andy Lutomirski <luto@...capital.net>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Alexander Larsson <alexl@...hat.com>,
	Cosimo Cecchi <cosimo@...lessm.com>,
	Dan Nicholson <nicholson@...lessm.com>,
	libc-alpha <libc-alpha@...rceware.org>,
	Rajalakshmi Srinivasaraghavan <raji@...ux.vnet.ibm.com>,
	Linux-Arch <linux-arch@...r.kernel.org>
Subject: Re: [PATCH] x86: Wire up 32-bit direct socket calls

On 09/02/2015 02:48 AM, Geert Uytterhoeven wrote:
> 
> Should all other architectures follow suit?
> Or should we follow the s390 approach:
> 

It is up to the maintainer(s), largely dependent on how likely you are
going to want to support this in your libc, but in general, socketcall
is an abomination which there is no reason not to bypass.

So follow suit unless you have a strong reason not to.

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