From: Kees Cook <keescook@chromium.org>
To: Norbert Lange <nolange79@gmail.com>
Cc: Christian Brauner <brauner@kernel.org>,
Laurent Vivier <laurent@vivier.eu>,
linux-kernel@vger.kernel.org, linux-api@vger.kernel.org,
linux-fsdevel@vger.kernel.org,
containers@lists.linux-foundation.org, jan.kiszka@siemens.com,
jannh@google.com, avagin@gmail.com, dima@arista.com,
James.Bottomley@hansenpartnership.com
Subject: Re: [PATCH v8 1/1] ns: add binfmt_misc to the user namespace
Date: Tue, 10 Oct 2023 17:36:07 -0700 [thread overview]
Message-ID: <202310101735.94C17F0@keescook> (raw)
In-Reply-To: <CADYdroNw5ZPPUqXQ5Psb8ffzi47SzvJAixQgxm+vsmV9eX_kYg@mail.gmail.com>
On Wed, Sep 06, 2023 at 12:28:27PM +0200, Norbert Lange wrote:
> Am Mi., 12. Juli 2023 um 21:40 Uhr schrieb Kees Cook <keescook@chromium.org>:
> >
> > On Fri, Jun 30, 2023 at 11:06:59AM +0200, Christian Brauner wrote:
> > > On Fri, Jun 30, 2023 at 10:52:22AM +0200, Laurent Vivier wrote:
> > > > Hi Norbert,
> > > >
> > > > Le 30/06/2023 à 10:38, Norbert Lange a écrit :
> > > > > Any news on this? What remains to be done, who needs to be harrassed?
> > > > >
> > > > > Regards, Norbert
> > > >
> > > > Christian was working on a new version but there is no update for 1 year.
> > > >
> > > > [PATCH v2 1/2] binfmt_misc: cleanup on filesystem umount
> > > > https://lkml.org/lkml/2021/12/16/406
> > > > [PATCH v2 2/2] binfmt_misc: enable sandboxed mounts
> > > > https://lkml.org/lkml/2021/12/16/407
> > > >
> > > > And personally I don't have the time to work on this.
> > >
> > > I've actually rebased this a few weeks ago:
> > > https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git/log/?h=vfs.binfmt_misc
> > > It has Acks, it's done. The only thing back then was Kees had wanted to
> > > take this but never did. I'll ping him.
> >
> > Hi! Can you resend this now that the merge window is closed? I looked at
> > it in your tree and it seems okay. I remain a bit nervous about exposing
> > it to unpriv access, but I'd like to give it a try. It'd be very useful!
> >
> > -Kees
> >
> > --
> > Kees Cook
>
> Hate to be that guy, but did anything move closer towards upstream
> since that post?
No rebase was needed -- I've dropped this in -next now. Let's see how it
goes!
--
Kees Cook
next prev parent reply other threads:[~2023-10-11 0:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-16 9:12 [PATCH v8 0/1] ns: introduce binfmt_misc namespace Laurent Vivier
2019-12-16 9:12 ` [PATCH v8 1/1] ns: add binfmt_misc to the user namespace Laurent Vivier
2019-12-16 19:08 ` Jann Horn
2019-12-16 20:05 ` Laurent Vivier
2019-12-16 22:53 ` Jann Horn
2021-01-08 8:22 ` Jan Kiszka
2021-01-08 8:22 ` Jan Kiszka
2021-01-18 19:51 ` Laurent Vivier
2021-01-18 19:51 ` Laurent Vivier
2023-06-30 8:38 ` Norbert Lange
2023-06-30 8:52 ` Laurent Vivier
2023-06-30 9:06 ` Christian Brauner
2023-07-12 19:40 ` Kees Cook
2023-09-06 10:28 ` Norbert Lange
2023-10-11 0:36 ` Kees Cook [this message]
2019-12-16 9:46 ` [PATCH v8 0/1] ns: introduce binfmt_misc namespace Christian Brauner
2019-12-16 9:53 ` Laurent Vivier
2019-12-16 10:06 ` Christian Brauner
2019-12-16 10:08 ` Laurent Vivier
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=202310101735.94C17F0@keescook \
--to=keescook@chromium.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=avagin@gmail.com \
--cc=brauner@kernel.org \
--cc=containers@lists.linux-foundation.org \
--cc=dima@arista.com \
--cc=jan.kiszka@siemens.com \
--cc=jannh@google.com \
--cc=laurent@vivier.eu \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nolange79@gmail.com \
/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.