From: Pratyush Yadav <pratyush@kernel.org>
To: Alexander Graf <graf@amazon.com>, Mike Rapoport <rppt@kernel.org>,
Pasha Tatashin <pasha.tatashin@soleen.com>,
Pratyush Yadav <pratyush@kernel.org>,
Hugh Dickins <hughd@google.com>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Jason Gunthorpe <jgg@nvidia.com>,
Samiullah Khawaja <skhawaja@google.com>,
kexec@lists.infradead.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/2] mm: memfd_luo: preserve file seals
Date: Mon, 16 Feb 2026 19:59:31 +0100 [thread overview]
Message-ID: <20260216185946.1215770-1-pratyush@kernel.org> (raw)
From: "Pratyush Yadav (Google)" <pratyush@kernel.org>
Hi,
This series adds support for preserving file seals when preserving a
memfd using LUO. Patch 1 exports some memfd seal manipulation functions
and patch 2 adds support for preserving them. Since it makes changes to
the serialized data structure for memfd, it also bumps the version
number.
Changes in v2:
- Define the set of seals supported by this version. Support for any
other seal would need a version bump. Make sure the memfd only has
this set of seals. Reject any that don't.
- Make seals a u32 since uABI defined it as an int. Change the
__reserved into flags.
Pratyush Yadav (Google) (2):
memfd: export memfd_{add,get}_seals()
mm: memfd_luo: preserve file seals
include/linux/kho/abi/memfd.h | 18 +++++++++++++++++-
include/linux/memfd.h | 12 ++++++++++++
mm/memfd.c | 4 ++--
mm/memfd_luo.c | 35 +++++++++++++++++++++++++++++++++--
4 files changed, 64 insertions(+), 5 deletions(-)
--
2.53.0.335.g19a08e0c02-goog
next reply other threads:[~2026-02-16 19:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-16 18:59 Pratyush Yadav [this message]
2026-02-16 18:59 ` [PATCH v2 1/2] memfd: export memfd_{add,get}_seals() Pratyush Yadav
2026-02-16 18:59 ` [PATCH v2 2/2] mm: memfd_luo: preserve file seals Pratyush Yadav
2026-02-17 21:51 ` [PATCH v2 0/2] " Samiullah Khawaja
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=20260216185946.1215770-1-pratyush@kernel.org \
--to=pratyush@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=graf@amazon.com \
--cc=hughd@google.com \
--cc=jgg@nvidia.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pasha.tatashin@soleen.com \
--cc=rppt@kernel.org \
--cc=skhawaja@google.com \
/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