[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK8P3a2TqHVyuPpQrghS8LfrvBffavsAFA5XC20Unf89CssRPw@mail.gmail.com>
Date: Thu, 16 May 2019 12:57:34 +0200
From: Arnd Bergmann <arnd@...db.de>
To: Roman Penyaev <rpenyaev@...e.de>
Cc: Azat Khuzhin <azat@...event.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Al Viro <viro@...iv.linux.org.uk>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Linux FS-devel Mailing List <linux-fsdevel@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3 13/13] epoll: implement epoll_create2() syscall
On Thu, May 16, 2019 at 12:20 PM Roman Penyaev <rpenyaev@...e.de> wrote:
>
> On 2019-05-16 12:03, Arnd Bergmann wrote:
> > On Thu, May 16, 2019 at 10:59 AM Roman Penyaev <rpenyaev@...e.de>
> > wrote:
> >>
> >> epoll_create2() is needed to accept EPOLL_USERPOLL flags
> >> and size, i.e. this patch wires up polling from userspace.
> >
> > Could you add the system call to all syscall*.tbl files at the same
> > time here?
>
> For all other archs, you mean? Sure. But what is the rule of thumb?
> Sometimes people tend to add to the most common x86 and other tables
> are left untouched, but then you commit the rest, e.g.
>
> commit 39036cd2727395c3369b1051005da74059a85317
> Author: Arnd Bergmann <arnd@...db.de>
> Date: Thu Feb 28 13:59:19 2019 +0100
>
> arch: add pidfd and io_uring syscalls everywhere
We only recently introduced syscall.tbl files in a common format,
which makes it much easier to add new ones. I hope we can
do it for all architectures right away from now on.
I just noticed that the new mount API assigns six new system
calls as well, but did not use the same numbers across
architectures. I hope we can still rectify that before -rc1
and use the next available ones (428..433), then yours should
be 434 on all architectures, with the exception of arch/alpha.
Arnd
Powered by blists - more mailing lists