From: Andrei Vagin <avagin@gmail.com>
To: Kees Cook <keescook@chromium.org>
Cc: Christian Brauner <brauner@kernel.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Alexey Izbyshev <izbyshev@ispras.ru>,
Florian Weimer <fweimer@redhat.com>,
Dmitry Safonov <0x7f454c46@gmail.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: Potentially undesirable interactions between vfork() and time namespaces
Date: Sun, 11 Sep 2022 15:51:41 -0700 [thread overview]
Message-ID: <CANaxB-yhmfRru4+n_+Q39QpkTzZjBHqkoq3JFwAG9mXDd0bjKA@mail.gmail.com> (raw)
In-Reply-To: <202209110810.F7352A26@keescook>
On Sun, Sep 11, 2022 at 8:12 AM Kees Cook <keescook@chromium.org> wrote:
>
> On Fri, Sep 09, 2022 at 09:51:58AM +0200, Christian Brauner wrote:
> > As stated above the proposed exec behavior we currently clearly emulate
> > in userspace. So that part is fine.
>
> It's not clear to me yet what the right solution is from this thread so
> far... what's needed for v6.0 release (since we're quickly running out
> of release candidates)?
Kees,
I think we reached a consensus to go with Eric's idea. We will send
the patch shortly.
Thanks,
Andrei
prev parent reply other threads:[~2022-09-11 22:51 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
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 [this message]
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=CANaxB-yhmfRru4+n_+Q39QpkTzZjBHqkoq3JFwAG9mXDd0bjKA@mail.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