From: Laurent Vivier <laurent@vivier.eu>
To: Norbert Lange <nolange79@gmail.com>,
linux-kernel@vger.kernel.org,
Christian Brauner <brauner@kernel.org>
Cc: 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: Fri, 30 Jun 2023 10:52:22 +0200 [thread overview]
Message-ID: <e8161622-beb0-d8d5-6501-f0bee76a372d@vivier.eu> (raw)
In-Reply-To: <20230630083852.3988-1-norbert.lange@andritz.com>
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.
Thanks,
Laurent
next prev parent reply other threads:[~2023-06-30 8:52 UTC|newest]
Thread overview: 17+ 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-18 19:51 ` Laurent Vivier
2023-06-30 8:38 ` Norbert Lange
2023-06-30 8:52 ` Laurent Vivier [this message]
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
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=e8161622-beb0-d8d5-6501-f0bee76a372d@vivier.eu \
--to=laurent@vivier.eu \
--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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).