From: Pasha Tatashin <pasha.tatashin@soleen.com>
To: David Carlier <devnexen@gmail.com>
Cc: akpm@linux-foundation.org, pratyush@kernel.org,
pasha.tatashin@soleen.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] mm/memfd_luo: document preservation of file seals
Date: Fri, 1 May 2026 19:41:02 +0000 [thread overview]
Message-ID: <afUBwC3oPTHdI84y@plex> (raw)
In-Reply-To: <20260423125648.152113-2-devnexen@gmail.com>
On 04-23 13:56, David Carlier wrote:
> Commit 8a552d68a86e ("mm: memfd_luo: preserve file seals") started
> preserving file seals across live update and restoring them via
> memfd_add_seals() on retrieve, but the DOC header was not updated and
> still listed seals under "Non-Preserved Properties" as being unsealed
> on restore.
>
> Move the Seals entry to the "Preserved Properties" section and describe
> the actual behavior, including the MEMFD_LUO_ALL_SEALS restriction that
> both preserve and retrieve enforce.
>
> Fixes: 8a552d68a86e ("mm: memfd_luo: preserve file seals")
> Signed-off-by: David Carlier <devnexen@gmail.com>
Reviewed-by: Pasha Tatashin <pasha.tatashin@soleen.com>
next prev parent reply other threads:[~2026-05-01 19:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-23 12:56 [PATCH 1/2] mm/memfd_luo: reject memfds whose page count exceeds UINT_MAX David Carlier
2026-04-23 12:56 ` [PATCH 2/2] mm/memfd_luo: document preservation of file seals David Carlier
2026-05-01 19:41 ` Pasha Tatashin [this message]
2026-05-04 8:07 ` Pratyush Yadav
2026-05-01 18:59 ` [PATCH 1/2] mm/memfd_luo: reject memfds whose page count exceeds UINT_MAX Pasha Tatashin
2026-05-01 19:26 ` David CARLIER
2026-05-01 19:38 ` Pasha Tatashin
2026-05-04 8:05 ` Pratyush Yadav
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=afUBwC3oPTHdI84y@plex \
--to=pasha.tatashin@soleen.com \
--cc=akpm@linux-foundation.org \
--cc=devnexen@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pratyush@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.