From: Andrei Vagin <avagin@gmail.com>
To: Alexey Izbyshev <izbyshev@ispras.ru>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
Florian Weimer <fweimer@redhat.com>,
Christian Brauner <brauner@kernel.org>,
Dmitry Safonov <0x7f454c46@gmail.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Kees Cook <keescook@chromium.org>
Subject: Re: Potentially undesirable interactions between vfork() and time namespaces
Date: Fri, 2 Sep 2022 10:28:29 -0700 [thread overview]
Message-ID: <YxI9PbdWsCmJe1Pz@gmail.com> (raw)
In-Reply-To: <bdff6cf478fc29c80997a623a57dae5f@ispras.ru>
On Fri, Sep 02, 2022 at 08:01:57PM +0300, Alexey Izbyshev wrote:
> On 2022-09-01 21:11, Eric W. Biederman wrote:
<snip>
> > static int check_setns_flags(unsigned long flags)
> > {
> > if (!flags || (flags & ~(CLONE_NEWNS | CLONE_NEWUTS | CLONE_NEWIPC |
> >
> >
> >
> > To keep things from being too confusing it probably makes sense to
> > rename the nsproxy variable from time_ns_for_children to
> > time_ns_for_new_mm. Likewise timens_on_fork can be renamed
> > timens_on_new_mm.
> >
> Do you imply renaming "/proc/[pid]/ns/time_for_children" as well, or will it
> be preserved for compatibility?
I don't think this is possible. It is used by a few tools already.
next prev parent reply other threads:[~2022-09-02 17:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-30 19:49 Alexey Izbyshev
2022-08-31 1:18 ` Andrei Vagin
2022-09-01 3:45 ` Andrei Vagin
2022-09-01 4:21 ` Florian Weimer
2022-09-01 15:49 ` Alexey Izbyshev
2022-09-01 18:11 ` Eric W. Biederman
2022-09-02 16:14 ` Andrei Vagin
2022-09-02 16:39 ` Alexey Izbyshev
2022-09-02 17:20 ` Andrei Vagin
2022-09-02 17:01 ` Alexey Izbyshev
2022-09-02 17:28 ` Andrei Vagin [this message]
2022-09-06 22:16 ` Eric W. Biederman
2022-09-07 5:33 ` Alexey Izbyshev
2022-09-07 17:15 ` Andrei Vagin
2022-09-08 8:10 ` Christian Brauner
2022-09-08 22:13 ` Eric W. Biederman
2022-09-09 7:51 ` Christian Brauner
2022-09-11 15:12 ` Kees Cook
2022-09-11 22:51 ` Andrei Vagin
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=YxI9PbdWsCmJe1Pz@gmail.com \
--to=avagin@gmail.com \
--cc=0x7f454c46@gmail.com \
--cc=brauner@kernel.org \
--cc=ebiederm@xmission.com \
--cc=fweimer@redhat.com \
--cc=izbyshev@ispras.ru \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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