From: Kees Cook <keescook@chromium.org>
To: Andrei Vagin <avagin@gmail.com>
Cc: Andrei Vagin <avagin@google.com>,
linux-kernel@vger.kernel.org,
Alexey Izbyshev <izbyshev@ispras.ru>,
Christian Brauner <brauner@kernel.org>,
Dmitry Safonov <0x7f454c46@gmail.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Florian Weimer <fweimer@redhat.com>
Subject: Re: [PATCH 1/2] fs/exec: switch timens when a task gets a new mm
Date: Fri, 23 Sep 2022 22:02:27 -0700 [thread overview]
Message-ID: <202209232159.BA0DA829@keescook> (raw)
In-Reply-To: <CANaxB-xGhJM4Boo-_fc2=kTE=0RpAL1CUxisNpvzpME_WNM_sQ@mail.gmail.com>
On Thu, Sep 22, 2022 at 06:47:46PM -0700, Andrei Vagin wrote:
> On Wed, Sep 21, 2022 at 8:29 PM Kees Cook <keescook@chromium.org> wrote:
> ...
> >
> > This looks good -- my intention is for this to go into -next after the
> > v6.1 merge window closes. Does that match everyone's expectations?
> >
>
> This works for me.
>
> If everything goes well, it will be merged to v6.2. Do I understand this right?
Right, that's what I'm expecting. :)
--
Kees Cook
next prev parent reply other threads:[~2022-09-24 5:02 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 [this message]
2022-10-18 7:21 ` Kees Cook
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=202209232159.BA0DA829@keescook \
--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.