public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Michael Opdenacker <michael.opdenacker@bootlin.com>
To: Luca Bocassi <luca.boccassi@gmail.com>,
	openembedded-core@lists.openembedded.org
Cc: YP docs mailing list <docs@lists.yoctoproject.org>
Subject: Re: [OE-core] [PATCH 2/2] mount-copybind: add MOUNT_COPYBIND_AVOID_OVERLAYFS env var to skip OverlayFS
Date: Mon, 28 Mar 2022 17:30:21 +0200	[thread overview]
Message-ID: <2c8e51a2-fd18-9781-7686-21d7a5376443@bootlin.com> (raw)
In-Reply-To: <20220325184032.1880706-2-luca.boccassi@gmail.com>

Hi Luca,

On 3/25/22 19:40, Luca Bocassi wrote:
> From: Luca Boccassi <luca.boccassi@microsoft.com>
>
> In some cases we don't want to even attempt to set up OverlayFS, for
> example because SELinux in enforcing mode would kill the process
> attempting to use the mount. See:
>
> https://lore.kernel.org/all/CA+FmFJBDwt52Z-dVGfuUcnRMiMtGPhK4cCQJ=J_fg0r3x-b6ng@mail.gmail.com/T/#mef98aa406324096d1889d3d467251f30456f403c
>
> If MOUNT_COPYBIND_AVOID_OVERLAYFS=1 is set, skip directly to copy and
> bind mount.
>
> Signed-off-by: Luca Boccassi <luca.boccassi@microsoft.com>


Thanks for the patch!
Now that the patch is merged, would you mind proposing a patch to add a
description of it to the documentation? You'll probably do it better
than I would.

Thanks in advance
Michael.

-- 
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com



  reply	other threads:[~2022-03-28 15:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-25 18:40 [PATCH 1/2] mount-copybind: fix shellcheck warning luca.boccassi
2022-03-25 18:40 ` [PATCH 2/2] mount-copybind: add MOUNT_COPYBIND_AVOID_OVERLAYFS env var to skip OverlayFS luca.boccassi
2022-03-28 15:30   ` Michael Opdenacker [this message]
2022-03-28 15:32     ` [OE-core] " Luca Boccassi
2022-03-28 16:08       ` Michael Opdenacker

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=2c8e51a2-fd18-9781-7686-21d7a5376443@bootlin.com \
    --to=michael.opdenacker@bootlin.com \
    --cc=docs@lists.yoctoproject.org \
    --cc=luca.boccassi@gmail.com \
    --cc=openembedded-core@lists.openembedded.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