From: "Mickaël Salaün" <mic@digikod.net>
To: Sasha Levin <sashal@kernel.org>
Cc: stable@vger.kernel.org, "Günther Noack" <gnoack3000@gmail.com>,
"Christian Brauner" <brauner@kernel.org>,
"Günther Noack" <gnoack@google.com>
Subject: Re: [PATCH 6.1.y] landlock: Require LANDLOCK_ACCESS_FS_MAKE_REG for whiteout creation
Date: Wed, 9 Sep 2026 20:18:53 +0200 [thread overview]
Message-ID: <20260909.Co6Phai8aKoh@digikod.net> (raw)
In-Reply-To: <2026-09-05-daily-reply-0020-landlock-whiteout-6-1@kernel.org>
On Sun, Sep 06, 2026 at 09:32:50AM -0400, Sasha Levin wrote:
> > Whiteout objects are used in the upper layer of an OverlayFS to
> > indicate that the file with this name does not exist in the unified
> > view, even if it is present in one of the lower layer file systems.
> >
> > For the userspace implementations of OverlayFS (fuse-overlayfs),
> > whiteout objects can be created from userspace as well:
>
> Queued for 6.1, thanks. Note: 6.1 is missing 49c9e09d9610 ("landlock: Fix
> handling of disconnected directories"), one of the two prerequisites this
> commit's own message names -- 6.12 and 6.6 already carry it. The whiteout
> check itself is still correct and worth having, but if a disconnected/
> bind-mounted directory is involved on 6.1 specifically the enforcement may
> not be reliable yet. Could you send 49c9e09d9610 as a follow-up for 6.1.y?
Hi Sasha,
These dependencies are indeed required to properly apply the patch, and
they are in fact fixes too (that failed to apply without changes). I'm
preparing a few backported patches (including these dependencies) that
I'll send this week.
Mickaël
next prev parent reply other threads:[~2026-09-09 18:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 14:01 FAILED: patch "[PATCH] landlock: Require LANDLOCK_ACCESS_FS_MAKE_REG for whiteout" failed to apply to 6.1-stable tree gregkh
2026-09-04 18:58 ` [PATCH 6.1.y] landlock: Require LANDLOCK_ACCESS_FS_MAKE_REG for whiteout creation Günther Noack
2026-09-06 13:32 ` Sasha Levin
2026-09-09 18:18 ` Mickaël Salaün [this message]
2026-09-17 15:00 ` [PATCH 6.1.y 1/4] landlock: Fix handling of disconnected directories Mickaël Salaün
2026-09-18 0:52 ` Sasha Levin
2026-09-17 15:00 ` [PATCH 6.1.y 2/4] selftests/landlock: Add tests for access through disconnected paths Mickaël Salaün
2026-09-17 15:00 ` [PATCH 6.1.y 3/4] selftests/landlock: Add disconnected leafs and branch test suites Mickaël Salaün
2026-09-18 0:52 ` Sasha Levin
2026-09-17 15:00 ` [PATCH 6.1.y 4/4] selftests/landlock: Add tests for whiteout object creation Mickaël Salaün
2026-09-18 19:45 ` Sasha Levin
2026-09-23 16:14 ` [PATCH 6.1.y v2] " Mickaël Salaün
2026-09-24 17:13 ` Sasha Levin
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=20260909.Co6Phai8aKoh@digikod.net \
--to=mic@digikod.net \
--cc=brauner@kernel.org \
--cc=gnoack3000@gmail.com \
--cc=gnoack@google.com \
--cc=sashal@kernel.org \
--cc=stable@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.