From: joeyli <jlee@suse.com>
To: Lorenzo Stoakes <ljs@kernel.org>
Cc: Chun-Yi Lee <joeyli.kernel@gmail.com>,
"Rafael J . Wysocki" <rafael@kernel.org>,
David Howells <dhowells@redhat.com>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Matthew Garrett <mjg59@srcf.ucam.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Danilo Krummrich <dakr@kernel.org>,
driver-core@lists.linux.dev, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH v2] debugfs: Fix lockdown check for mmap_prepare
Date: Mon, 15 Jun 2026 22:54:06 +0800 [thread overview]
Message-ID: <20260615145406.GQ11413@linux-l9pv.suse> (raw)
In-Reply-To: <ai_fWlr61AzrNrDz@lucifer>
On Mon, Jun 15, 2026 at 12:18:29PM +0100, Lorenzo Stoakes wrote:
> On Mon, Jun 15, 2026 at 06:47:50PM +0800, Chun-Yi Lee wrote:
> > From: Chun-Yi Lee <jlee@suse.com>
> >
> > Commit 651fdda8406d ("relay: update relay to use mmap_prepare")
> > changed the `mmap` file operation to `mmap_prepare` for relayfs, but
> > the lockdown check in debugfs was not updated accordingly.
> >
> > This prevents debugfs from being locked down when the kernel is in
> > integrity mode if a file uses `mmap_prepare` but not `mmap`.
> >
> > Since the conversion to `mmap_prepare` across the kernel is not yet
> > complete, update the lockdown check to look for both `mmap` and
> > `mmap_prepare` to ensure comprehensive coverage.
> >
> > Fixes: 651fdda8406d ("relay: update relay to use mmap_prepare")
> > Signed-off-by: Chun-Yi Lee <jlee@suse.com>
>
> LGTM so:
>
> Reviewed-by: Lorenzo Stoakes <ljs@kernel.org>
>
Thanks for Lorenzo's review!
Joey Lee
prev parent reply other threads:[~2026-06-15 14:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-15 10:47 [PATCH v2] debugfs: Fix lockdown check for mmap_prepare Chun-Yi Lee
2026-06-15 11:18 ` Lorenzo Stoakes
2026-06-15 14:54 ` joeyli [this message]
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=20260615145406.GQ11413@linux-l9pv.suse \
--to=jlee@suse.com \
--cc=andy.shevchenko@gmail.com \
--cc=dakr@kernel.org \
--cc=dhowells@redhat.com \
--cc=driver-core@lists.linux.dev \
--cc=gregkh@linuxfoundation.org \
--cc=joeyli.kernel@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ljs@kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=rafael@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
/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