mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christian Brauner <brauner@kernel.org>
To: "Phillip Lougher" <phillip@squashfs.org.uk>,
	"Michael Weiß" <michael.weiss@aisec.fraunhofer.de>
Cc: Christian Brauner <brauner@kernel.org>,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	squashfs-devel@lists.sourceforge.net
Subject: Re: [PATCH 1/1] squashfs: enable idmapped mounts
Date: Sun,  6 Nov 2022 12:51:55 +0100	[thread overview]
Message-ID: <166773513784.1468888.296199198590720418.b4-ty@kernel.org> (raw)
In-Reply-To: <20221024191552.55951-1-michael.weiss@aisec.fraunhofer.de>

From: Christian Brauner (Microsoft) <brauner@kernel.org>

On Mon, 24 Oct 2022 21:15:52 +0200, Michael Weiß wrote:
> For squashfs all needed functionality for idmapped mounts is already
> implemented by the generic handlers in the VFS. Thus, it is sufficient
> to just enable the corresponding FS_ALLOW_IDMAP flag to support
> idmapped mounts.
> 
> We use this for unprivileged (user namespaced) containers based on
> squashfs images as rootfs in GyroidOS.
> 
> [...]

Hey Phillip,

Michael reminded me about this patch just now. I've picked this up now so it
can make it into the next mw. Phillip, in case you'll pick this up just tell me
and I'll drop it.

[1/1] squashfs: enable idmapped mounts
      commit: 01546f1d7142f27002789e8626a32b20d5853a48

Thanks!
Christian

  parent reply	other threads:[~2022-11-06 11:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-24 19:15 Michael Weiß
2022-10-25  7:46 ` Christian Brauner
2022-11-06 11:51 ` Christian Brauner [this message]
2022-11-06 17:56 ` Phillip Lougher

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=166773513784.1468888.296199198590720418.b4-ty@kernel.org \
    --to=brauner@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael.weiss@aisec.fraunhofer.de \
    --cc=phillip@squashfs.org.uk \
    --cc=squashfs-devel@lists.sourceforge.net \
    /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®