From: Kees Cook <keescook@chromium.org>
To: avagin@google.com
Cc: Kees Cook <keescook@chromium.org>,
fweimer@redhat.com, linux-kernel@vger.kernel.org,
ebiederm@xmission.com, izbyshev@ispras.ru, avagin@gmail.com,
0x7f454c46@gmail.com, brauner@kernel.org
Subject: Re: [PATCH 1/2] fs/exec: switch timens when a task gets a new mm
Date: Tue, 18 Oct 2022 00:21:08 -0700 [thread overview]
Message-ID: <166607766447.3775011.11893363509592656217.b4-ty@chromium.org> (raw)
In-Reply-To: <20220921003120.209637-1-avagin@google.com>
On Tue, 20 Sep 2022 17:31:19 -0700, Andrei Vagin wrote:
> From: Andrei Vagin <avagin@gmail.com>
>
> Changing a time namespace requires remapping a vvar page, so we don't want
> to allow doing that if any other tasks can use the same mm.
>
> Currently, we install a time namespace when a task is created with a new
> vm. exec() is another case when a task gets a new mm and so it can switch
> a time namespace safely, but it isn't handled now.
>
> [...]
Applied to for-next/execve, thanks!
[1/2] fs/exec: switch timens when a task gets a new mm
https://git.kernel.org/kees/c/f8e06046dd69
[2/2] selftests/timens: add a test for vfork+exit
https://git.kernel.org/kees/c/de8517320d01
--
Kees Cook
prev parent reply other threads:[~2022-10-18 7:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 0:31 [PATCH 1/2] fs/exec: switch timens when a task gets a new mm Andrei Vagin
2022-09-21 0:31 ` [PATCH 2/2] selftests/timens: add a test for vfork+exit Andrei Vagin
2022-10-09 16:10 ` Alexey Izbyshev
2022-10-13 17:46 ` Andrei Vagin
2022-10-13 22:15 ` Alexey Izbyshev
2022-10-13 17:31 ` [PATCH 2/2 v2] " Andrei Vagin
2022-09-22 3:29 ` [PATCH 1/2] fs/exec: switch timens when a task gets a new mm Kees Cook
2022-09-23 1:47 ` Andrei Vagin
2022-09-24 5:02 ` Kees Cook
2022-10-18 7:21 ` 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=166607766447.3775011.11893363509592656217.b4-ty@chromium.org \
--to=keescook@chromium.org \
--cc=0x7f454c46@gmail.com \
--cc=avagin@gmail.com \
--cc=avagin@google.com \
--cc=brauner@kernel.org \
--cc=ebiederm@xmission.com \
--cc=fweimer@redhat.com \
--cc=izbyshev@ispras.ru \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.