From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1752341AbbIKKPf (ORCPT <rfc822;w@1wt.eu>);
	Fri, 11 Sep 2015 06:15:35 -0400
Received: from mout.kundenserver.de ([212.227.126.187]:60234 "EHLO
	mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1751584AbbIKKPd (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Fri, 11 Sep 2015 06:15:33 -0400
From: Arnd Bergmann <arnd@arndb.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Heiko Carstens <heiko.carstens@de.ibm.com>,
        "H. Peter Anvin" <hpa@zytor.com>, Andy Lutomirski <luto@kernel.org>,
        X86 ML <x86@kernel.org>, Network Development <netdev@vger.kernel.org>,
        Tulio Magno Quites Machado Filho 
	<tuliom@linux.vnet.ibm.com>,
        Andy Lutomirski <luto@amacapital.net>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        Alexander Larsson <alexl@redhat.com>,
        Cosimo Cecchi <cosimo@endlessm.com>,
        Dan Nicholson <nicholson@endlessm.com>,
        libc-alpha <libc-alpha@sourceware.org>,
        Rajalakshmi Srinivasaraghavan <raji@linux.vnet.ibm.com>,
        Linux-Arch <linux-arch@vger.kernel.org>
Subject: Re: [PATCH] x86: Wire up 32-bit direct socket calls
Date: Fri, 11 Sep 2015 12:14:13 +0200
Message-ID: <2108882.tTxglVCXxY@wuerfel>
User-Agent: KMail/4.11.5 (Linux/3.16.0-10-generic; KDE/4.11.5; x86_64; ; )
In-Reply-To: <CAMuHMdXX31xZ4AS6FbeXLXgDn5UV5=0C3hrihuwDOP_abuJsBg@mail.gmail.com>
References: <cb5138299d37d5800e2d135b01a7667fa6115854.1436912629.git.luto@kernel.org> <49726621.LPTnfQXYGz@wuerfel> <CAMuHMdXX31xZ4AS6FbeXLXgDn5UV5=0C3hrihuwDOP_abuJsBg@mail.gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-Provags-ID: V03:K0:PBOC+H3iBqq8TlRneR+2VXapKwYzmNrAWmOEbp5z4Ak98ObKa3C
 0SMoPzBY5ZRFDPi+qpl6sYSDi09lx4hxSFI6uIPa5NSVpNPExHKf+LA7jRjlH134+bC7LyL
 1wc5eCQsurP9XW32c/P2xgwddjlBWjSOFJIF9UDVTWofLKXNMq7Jfa8a6IiA+ZC9hHfFuuI
 glgx9t2wWHUp3NBMYWZEw==
X-UI-Out-Filterresults: notjunk:1;V01:K0:gFAligquaTk=:IOj8zVxAOyd10Okw9S8R9+
 dZbEhumsPPCU1sXIFX8i5i9OQUjTeThIpPH9mIsvDdokPraGfIDtMktXdZNxdQFHpvfyUwEzL
 WBQVYH5Rm78A9H+kQYk4O+FNVEDaC7ozuf+8Pf26nWjo0I81WJwbvT4uNOXIqJp1zZB+EWulm
 FNeotoeL/8Jvcv8/mhFqEhzQRzX0Ku7QZsFioQcpaUeV1OtrjGSnlOOYtflSp50h2whyNQgsa
 FCm91fjMHvOMVofvRtY3cvIgB2djnqBK3dVKsg3MFaRZG0IIj99gRbtU1eYyhkz1uhXnxfCcE
 8KhRAgfZSWhE71XhNnfHBWRzJ0VRYHt+Uj/WKmrhmLB22hojdeUUqyZu+/MkofzCBDk2Q/9DU
 nNJY0elLcN3akb3fVTv9KzNxk8P7M/+C7I12YmpDPxsC0Vlsq6EmQEQoU1tstjzOAL3KRU82s
 5E9QtAI63KCPeLgSOfXEQmKKsYz8KJSjfs4/KQxWIb56Bp41BZKXwLhGlHlFZHXtum1gPJ6l5
 PHfhlpIK6FUfr0ZGjtTfI+YquL/qyWF7EPPhHTAuhDRRkOfVS0chyc9qgBA+d+/kqa1xratyW
 R1jg76vzSkjCqRzRNGSqhJWoHtWkTm5ZrgbvumprJ+nzIMdHCg4OvVQJhHMBOO6C9+aLn65Gr
 kgypmyczn1uyyBcxOT4yyTyd4yIfW+MVq41hEg7T06xKWypsCZwrohKSiKyAzgDQgafPPllPB
 WFfCA9OhCukQ7cFV
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Friday 11 September 2015 11:54:50 Geert Uytterhoeven wrote:
> To make sure I don't miss any (it seems I missed recvmmsg and sendmmsg for
> the socketcall case, sigh), this is the list of ipc syscalls to implement?
> 
>     sys_msgget
>     sys_msgctl
>     sys_msgrcv
>     sys_msgsnd
>     sys_semget
>     sys_semctl
>     sys_semtimedop
>     sys_shmget
>     sys_shmctl
>     sys_shmat
>     sys_shmdt
> 
> sys_semop() seems to be unneeded because it can be implemented using
> sys_semtimedop()?
> 

Yes, that list looks right. IPC also includes a set of six sys_mq_*
call, but I believe that everyone already has those as they are not
covered by sys_ipc.

For y2038 compatibility, we will likely add a new variant of
semtimedop that takes a 64-bit timespec. While the argument passed
there is a relative time that will never need to be longer than 68
years, we need to accommodate user space that defines timespec
in a sane way, and converting the argument in libc would be awkward.

	Arnd