From: Christian Brauner <christian@brauner.io>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
Oleg Nesterov <oleg@redhat.com>, Arnd Bergmann <arnd@arndb.de>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Kees Cook <keescook@chromium.org>,
Joel Fernandes <joel@joelfernandes.org>,
Thomas Gleixner <tglx@linutronix.de>, Tejun Heo <tj@kernel.org>,
David Howells <dhowells@redhat.com>, Jann Horn <jannh@google.com>,
Andrew Lutomirski <luto@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Aleksa Sarai <cyphar@cyphar.com>,
Al Viro <viro@zeniv.linux.org.uk>,
Android Kernel Team <kernel-team@android.com>
Subject: Re: [PATCH v2 1/2] pidfd: add P_PIDFD to waitid()
Date: Sat, 27 Jul 2019 21:45:52 +0200 [thread overview]
Message-ID: <20190727194552.xpudr7ou4wjowhew@brauner.io> (raw)
In-Reply-To: <CAHk-=whrh5+aHmgqP9YhZ-yzCtUWT8fPi08ZSJdxusx7aHXOQQ@mail.gmail.com>
On Sat, Jul 27, 2019 at 09:28:40AM -0700, Linus Torvalds wrote:
> Sorry to keep pestering about the patch series, but with the addition
> of P_PIDFD, I react once again..
That's fine. I don't at all mind being particular about how something
has to be done as long as the result is functional. In this case it
seems we'll end up with something cleaner overall, so sure.
I'll rework the snippets into the actual patch and resend. I'll leave
out the rcu-cleverness you suggested in the other mail though.
Christian
next prev parent reply other threads:[~2019-07-27 19:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-27 8:51 [PATCH v2 0/2] pidfd: waiting on processes through pidfds Christian Brauner
2019-07-27 8:52 ` [PATCH v2 1/2] pidfd: add P_PIDFD to waitid() Christian Brauner
2019-07-27 16:28 ` Linus Torvalds
2019-07-27 16:41 ` Linus Torvalds
2019-07-27 19:42 ` Christian Brauner
2019-07-27 16:49 ` Al Viro
2019-07-27 19:46 ` Christian Brauner
2019-07-27 19:45 ` Christian Brauner [this message]
2019-07-27 8:52 ` [PATCH v2 2/2] pidfd: add pidfd_wait tests 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=20190727194552.xpudr7ou4wjowhew@brauner.io \
--to=christian@brauner.io \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=cyphar@cyphar.com \
--cc=dhowells@redhat.com \
--cc=ebiederm@xmission.com \
--cc=jannh@google.com \
--cc=joel@joelfernandes.org \
--cc=keescook@chromium.org \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=oleg@redhat.com \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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
all inboxes | Powered by JetHome®