From: Kees Cook <keescook@chromium.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
Alexey Izbyshev <izbyshev@ispras.ru>,
Andrei Vagin <avagin@gmail.com>,
Christian Brauner <brauner@kernel.org>,
Dmitry Safonov <0x7f454c46@gmail.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Florian Weimer <fweimer@redhat.com>,
Kees Cook <keescook@chromium.org>
Subject: [GIT PULL] execve reverts for v6.0-rc7
Date: Mon, 19 Sep 2022 12:51:46 -0700 [thread overview]
Message-ID: <202209191245.B40A17BA51@keescook> (raw)
Hi Linus,
Please pull these execve reverts for v6.0-rc7. The recent work to
support time namespace unsharing turns out to have some undesirable
corner cases, so rather than allowing the API to stay exposed for
another release, it'd be best to remove it ASAP, with the replacement
getting another cycle of testing. Nothing is known to use this yet,
so no userspace breakage is expected. For more details, see:
https://lore.kernel.org/lkml/ed418e43ad28b8688cfea2b7c90fce1c@ispras.ru/
Also note that this is expected to introduce a small merge conflict for
the coming v6.1 merge window, as seen in linux-next:
https://lore.kernel.org/linux-next/20220914155533.70c10493@canb.auug.org.au/
Thanks!
-Kees
The following changes since commit 1c23f9e627a7b412978b4e852793c5e3c3efc555:
Linux 6.0-rc2 (2022-08-21 17:32:54 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/execve-v6.0-rc7
for you to fetch changes up to 33a2d6bc3480f9f8ac8c8def29854f98cc8bfee2:
Revert "fs/exec: allow to unshare a time namespace on vfork+exec" (2022-09-13 10:38:43 -0700)
----------------------------------------------------------------
execve reverts for v6.0-rc7
- Remove the recent "unshare time namespace on vfork+exec" feature (Andrei Vagin)
----------------------------------------------------------------
Andrei Vagin (2):
Revert "selftests/timens: add a test for vfork+exit"
Revert "fs/exec: allow to unshare a time namespace on vfork+exec"
fs/exec.c | 7 ---
kernel/fork.c | 5 +-
kernel/nsproxy.c | 3 +-
tools/testing/selftests/timens/Makefile | 2 +-
tools/testing/selftests/timens/vfork_exec.c | 90 -----------------------------
5 files changed, 3 insertions(+), 104 deletions(-)
delete mode 100644 tools/testing/selftests/timens/vfork_exec.c
--
Kees Cook
next reply other threads:[~2022-09-19 19:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-19 19:51 Kees Cook [this message]
2022-09-20 17:35 ` pr-tracker-bot
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=202209191245.B40A17BA51@keescook \
--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=izbyshev@ispras.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®