From: Kees Cook <keescook@chromium.org>
To: avagin@gmail.com, linux-kernel@vger.kernel.org,
0x7f454c46@gmail.com, brauner@kernel.org
Cc: Kees Cook <keescook@chromium.org>,
ebiederm@xmission.com, linux-mm@kvack.org, fweimer@redhat.com
Subject: Re: [PATCH 1/2] fs/exec: allow to unshare a time namespace on vfork+exec
Date: Wed, 15 Jun 2022 08:01:48 -0700 [thread overview]
Message-ID: <165530530544.261757.10728167525988459977.b4-ty@chromium.org> (raw)
In-Reply-To: <20220613060723.197407-1-avagin@gmail.com>
On Sun, 12 Jun 2022 23:07:22 -0700, Andrei Vagin wrote:
> Right now, a new process can't be forked in another time namespace
> if it shares mm with its parent. It is prohibited, because each time
> namespace has its own vvar page that is mapped into a process address
> space.
>
> When a process calls exec, it gets a new mm and so it could be "legal"
> to switch time namespace in that case. This was not implemented and
> now if we want to do this, we need to add another clone flag to not
> break backward compatibility.
>
> [...]
Applied to for-next/execve, thanks!
[1/2] fs/exec: allow to unshare a time namespace on vfork+exec
https://git.kernel.org/kees/c/133e2d3e81de
[2/2] testing/timens: add a test for vfork+exit
https://git.kernel.org/kees/c/6342140db660
--
Kees Cook
prev parent reply other threads:[~2022-06-15 15:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-13 6:07 Andrei Vagin
2022-06-13 6:07 ` [PATCH 2/2] testing/timens: add a test for vfork+exit Andrei Vagin
2022-06-14 21:14 ` [PATCH 1/2] fs/exec: allow to unshare a time namespace on vfork+exec Kees Cook
2022-06-15 7:52 ` Christian Brauner
2022-06-15 7:53 ` Florian Weimer
2022-06-15 8:00 ` Christian Brauner
2022-06-15 8:14 ` Florian Weimer
2022-06-15 8:53 ` Christian Brauner
2022-06-15 7:37 ` Christian Brauner
2022-06-15 15:01 ` Kees Cook [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=165530530544.261757.10728167525988459977.b4-ty@chromium.org \
--to=keescook@chromium.org \
--cc=0x7f454c46@gmail.com \
--cc=avagin@gmail.com \
--cc=brauner@kernel.org \
--cc=ebiederm@xmission.com \
--cc=fweimer@redhat.com \
--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