linux-api.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org (Eric W. Biederman)
To: Aleksa Sarai <asarai-l3A5Bk7waGM@public.gmane.org>
Cc: linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Linux Containers
	<containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>,
	Linus Torvalds
	<torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [GIT PULL] namespaces related fixes for v4.11-rc1
Date: Thu, 23 Feb 2017 14:29:45 +1300	[thread overview]
Message-ID: <8737f54rue.fsf@xmission.com> (raw)
In-Reply-To: <84361910-ba16-79ff-09cd-c76b3f66cc85-l3A5Bk7waGM@public.gmane.org> (Aleksa Sarai's message of "Thu, 23 Feb 2017 08:15:46 +1100")

Aleksa Sarai <asarai-l3A5Bk7waGM@public.gmane.org> writes:

>> The only known user of this prctl systemd
>> forks all children after the prctl.  So no userspace regressions will
>> occur.
>
> Note that runC and containerd (and thus Docker) as well as cri-o use the prctl
> as well -- to be able to collect exit codes from a non-child process (namely to
> collect the exit code from PID 1 in the container).

Are any of those affected by the change?  I would not expect so.  As it
would require having children or grand children whose exit codes you
don't want to collect.

Eric

  parent reply	other threads:[~2017-02-23  1:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-22 20:48 [GIT PULL] namespaces related fixes for v4.11-rc1 Eric W. Biederman
2017-02-22 21:15 ` Aleksa Sarai
     [not found]   ` <84361910-ba16-79ff-09cd-c76b3f66cc85-l3A5Bk7waGM@public.gmane.org>
2017-02-23  1:29     ` Eric W. Biederman [this message]
     [not found]       ` <8737f54rue.fsf-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org>
2017-02-23  2:21         ` Aleksa Sarai
2017-02-23  3:06         ` Andy Lutomirski

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=8737f54rue.fsf@xmission.com \
    --to=ebiederm-as9lmozglivwk0htik3j/w@public.gmane.org \
    --cc=asarai-l3A5Bk7waGM@public.gmane.org \
    --cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.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).