linux-kernel - Re: sys_recvmmsg: wire up or not?

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: <1263526369.724.399.camel@pasglop>
Date:	Fri, 15 Jan 2010 14:32:49 +1100
From:	Benjamin Herrenschmidt <benh@...nel.crashing.org>
To:	Russell King <rmk+lkml@....linux.org.uk>
Cc:	David Miller <davem@...emloft.net>, arnd@...db.de,
	geert@...ux-m68k.org, acme@...hat.com, linux-arch@...r.kernel.org,
	linux-kernel@...r.kernel.org, linux-m68k@...r.kernel.org
Subject: Re: sys_recvmmsg: wire up or not?

On Thu, 2010-01-14 at 09:33 +0000, Russell King wrote:
> On ARM, we used to use socketcall exclusively.  We've since added all
> the direct socket and IPC calls to our syscall table as part of the
> big EABI shakeup.  They certainly get used on EABI, whereas OABI has
> a choice.
> 
> They were made available in two stages - first the numbers were
> reserved
> and the calls were added to the call table.  A few years later, we
> exposed the syscall numbers in unistd.h.
> 
> It's now been almost 4 years since this was done, and there have been
> no bug reports. 

Agreed. It's definitely a switch we should do on powerpc. I'll look into
it after LCA.

Cheers,
Ben.


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