[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190419200521.5pr66nsdj3i7liip@brauner.io>
Date: Fri, 19 Apr 2019 22:05:22 +0200
From: Christian Brauner <christian@...uner.io>
To: torvalds@...ux-foundation.org, viro@...iv.linux.org.uk,
jannh@...gle.com, dhowells@...hat.com, oleg@...hat.com,
linux-api@...r.kernel.org, linux-kernel@...r.kernel.org
Cc: serge@...lyn.com, luto@...nel.org, arnd@...db.de,
ebiederm@...ssion.com, keescook@...omium.org, tglx@...utronix.de,
mtk.manpages@...il.com, akpm@...ux-foundation.org,
cyphar@...har.com, joel@...lfernandes.org, dancol@...gle.com,
Jann Horn <jann@...jh.net>
Subject: Re: [PATCH v3 0/4] clone: add CLONE_PIDFD
On Fri, Apr 19, 2019 at 02:09:00PM +0200, Christian Brauner wrote:
> Hey,
>
> /* v3 summary */
> After a brief discussion we decided to block CLONE_PIDFD with
> CLONE_THREAD for now. Not because it is not possible but because we
> don't have a use-case yet and blocking it makes the initial work for
> pidfd polling easier. However, it is possible to simply flick the
> switch later.
I have moved v3 into my for-next branch which means it should show up in
linux-next for some testing soon. All versions of the CLONE_PIDFD
patches are on top of v5.1-rc4.
Thanks!
Christian
Powered by blists - more mailing lists