From: "Dmitry V. Levin" <ldv@altlinux.org>
To: Christian Brauner <christian@brauner.io>
Cc: Jann Horn <jannh@google.com>, Oleg Nesterov <oleg@redhat.com>,
Arnd Bergmann <arnd@arndb.de>,
linux-api@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] samples: make pidfd-metadata fail gracefully on older kernels
Date: Sun, 23 Jun 2019 14:32:30 +0300 [thread overview]
Message-ID: <20190623113230.GC20697@altlinux.org> (raw)
In-Reply-To: <20190621221339.6yj4vg4zexv4y2j7@brauner.io>
[-- Attachment #1: Type: text/plain, Size: 505 bytes --]
On Sat, Jun 22, 2019 at 12:13:39AM +0200, Christian Brauner wrote:
[...]
> Out of curiosity: what makes the new flag different than say
> CLONE_NEWCGROUP or any new clone flag that got introduced?
> CLONE_NEWCGROUP too would not be detectable apart from the method I gave
> you above; same for other clone flags. Why are you so keen on being able
> to detect this flag when other flags didn't seem to matter that much.
I wasn't following uapi changes closely enough those days. ;)
--
ldv
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2019-06-23 11:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-20 3:11 [PATCH] samples: make pidfd-metadata fail gracefully on older kernels Dmitry V. Levin
2019-06-20 10:31 ` Christian Brauner
2019-06-20 11:00 ` Dmitry V. Levin
2019-06-20 11:10 ` Christian Brauner
2019-06-21 17:06 ` Dmitry V. Levin
2019-06-21 22:13 ` Christian Brauner
2019-06-23 11:27 ` [PATCH 1/2] CLONE_PIDFD: do not use the value pointed by parent_tidptr Dmitry V. Levin
2019-06-23 11:28 ` [PATCH 2/2] samples: make pidfd-metadata fail gracefully on older kernels Dmitry V. Levin
2019-06-24 9:50 ` Christian Brauner
2019-06-24 9:49 ` [PATCH 1/2] CLONE_PIDFD: do not use the value pointed by parent_tidptr Christian Brauner
2019-06-24 11:59 ` Christian Brauner
2019-06-24 13:45 ` Dmitry V. Levin
2019-06-24 13:49 ` Christian Brauner
2019-06-23 11:32 ` Dmitry V. Levin [this message]
2019-06-24 9:52 ` [PATCH] samples: make pidfd-metadata fail gracefully on older kernels 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=20190623113230.GC20697@altlinux.org \
--to=ldv@altlinux.org \
--cc=arnd@arndb.de \
--cc=christian@brauner.io \
--cc=jannh@google.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
/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