From: Arnd Bergmann <arnd@arndb.de>
To: Christian Brauner <christian@brauner.io>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2] clone3 fixes
Date: Sun, 14 Jul 2019 22:07:13 +0200 [thread overview]
Message-ID: <CAK8P3a23y0UFbu-po-Umh-=9DUTpRyzRkB=RxJd1A+YJVTTGrA@mail.gmail.com> (raw)
In-Reply-To: <20190714192205.27190-1-christian@brauner.io>
On Sun, Jul 14, 2019 at 9:22 PM Christian Brauner <christian@brauner.io> wrote:
>
> Hey everyone,
>
> Here are two small fixes/improvements for the clone3 syscall that I plan
> on sending soon.
>
> The first patches reserves the clone3 syscalls number 435 across all
> architectures by placing a commit in the corresponding syscall tables of
> architectures that do not yet implement clone3. This is done to preserve
> the identical numbering for all new syscalls that Arnd introduced.
>
> The second patch dates back to a discussion with Arnd when I suggested
> reserving the syscall number. Arnd suggested to ensure that we catch all
> arches that do implement clone3 without explicitly setting
> __ARCH_WANT_SYS_CLONE3.
Both patches
Reviewed-by: Arnd Bergmann <arnd@arndb.de>
next prev parent reply other threads:[~2019-07-14 20:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-14 19:22 [PATCH 0/2] clone3 fixes Christian Brauner
2019-07-14 19:22 ` [PATCH 1/2] arch: mark syscall number 435 reserved for clone3 Christian Brauner
2019-07-15 13:56 ` Christian Borntraeger
2019-07-15 14:29 ` Christian Brauner
2019-07-16 13:06 ` Christian Brauner
2019-07-16 18:53 ` Sven Schnelle
2019-07-16 18:55 ` Christian Brauner
2019-07-16 20:13 ` Helge Deller
2019-07-19 10:18 ` Michael Ellerman
2019-07-19 10:25 ` Christian Brauner
2019-07-19 11:13 ` Michael Ellerman
2019-07-19 12:20 ` Christian Brauner
2019-07-14 19:22 ` [PATCH 2/2] unistd: protect clone3 via __ARCH_WANT_SYS_CLONE3 Christian Brauner
2019-07-14 20:07 ` Arnd Bergmann [this message]
2019-07-14 22:30 ` [PATCH 0/2] clone3 fixes Christian Brauner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAK8P3a23y0UFbu-po-Umh-=9DUTpRyzRkB=RxJd1A+YJVTTGrA@mail.gmail.com' \
--to=arnd@arndb.de \
--cc=christian@brauner.io \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).