From: Pasha Tatashin <pasha.tatashin@soleen.com>
To: pratyush@kernel.org, jasonmiu@google.com, graf@amazon.com,
pasha.tatashin@soleen.com, rppt@kernel.org, dmatlack@google.com,
rientjes@google.com, corbet@lwn.net, rdunlap@infradead.org,
ilpo.jarvinen@linux.intel.com, kanie@linux.alibaba.com,
ojeda@kernel.org, aliceryhl@google.com, masahiroy@kernel.org,
akpm@linux-foundation.org, tj@kernel.org, yoann.congal@smile.fr,
mmaurer@google.com, roman.gushchin@linux.dev,
chenridong@huawei.com, axboe@kernel.dk, mark.rutland@arm.com,
jannh@google.com, vincent.guittot@linaro.org, hannes@cmpxchg.org,
dan.j.williams@intel.com, david@redhat.com,
joel.granados@kernel.org, rostedt@goodmis.org,
anna.schumaker@oracle.com, song@kernel.org, linux@weissschuh.net,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
linux-mm@kvack.org, gregkh@linuxfoundation.org,
tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
dave.hansen@linux.intel.com, x86@kernel.org, hpa@zytor.com,
rafael@kernel.org, dakr@kernel.org,
bartosz.golaszewski@linaro.org, cw00.choi@samsung.com,
myungjoo.ham@samsung.com, yesanishhere@gmail.com,
Jonathan.Cameron@huawei.com, quic_zijuhu@quicinc.com,
aleksander.lobakin@intel.com, ira.weiny@intel.com,
andriy.shevchenko@linux.intel.com, leon@kernel.org,
lukas@wunner.de, bhelgaas@google.com, wagi@kernel.org,
djeffery@redhat.com, stuart.w.hayes@gmail.com, ptyadav@amazon.de,
lennart@poettering.net, brauner@kernel.org,
linux-api@vger.kernel.org, linux-fsdevel@vger.kernel.org,
saeedm@nvidia.com, ajayachandra@nvidia.com, jgg@nvidia.com,
parav@nvidia.com, leonro@nvidia.com, witu@nvidia.com,
hughd@google.com, skhawaja@google.com, chrisl@kernel.org
Subject: [PATCH v7 11/22] mm: shmem: allow freezing inode mapping
Date: Sat, 22 Nov 2025 17:23:38 -0500 [thread overview]
Message-ID: <20251122222351.1059049-12-pasha.tatashin@soleen.com> (raw)
In-Reply-To: <20251122222351.1059049-1-pasha.tatashin@soleen.com>
From: Pratyush Yadav <ptyadav@amazon.de>
To prepare a shmem inode for live update, its index -> folio mappings
must be serialized. Once the mappings are serialized, they cannot change
since it would cause the serialized data to become inconsistent. This
can be done by pinning the folios to avoid migration, and by making sure
no folios can be added to or removed from the inode.
While mechanisms to pin folios already exist, the only way to stop
folios being added or removed are the grow and shrink file seals. But
file seals come with their own semantics, one of which is that they
can't be removed. This doesn't work with liveupdate since it can be
cancelled or error out, which would need the seals to be removed and the
file's normal functionality to be restored.
Introduce SHMEM_F_MAPPING_FROZEN to indicate this instead. It is
internal to shmem and is not directly exposed to userspace. It functions
similar to F_SEAL_GROW | F_SEAL_SHRINK, but additionally disallows hole
punching, and can be removed.
Signed-off-by: Pratyush Yadav <ptyadav@amazon.de>
Signed-off-by: Pasha Tatashin <pasha.tatashin@soleen.com>
---
include/linux/shmem_fs.h | 17 +++++++++++++++++
mm/shmem.c | 19 ++++++++++++++++---
2 files changed, 33 insertions(+), 3 deletions(-)
diff --git a/include/linux/shmem_fs.h b/include/linux/shmem_fs.h
index 650874b400b5..d34a64eafe60 100644
--- a/include/linux/shmem_fs.h
+++ b/include/linux/shmem_fs.h
@@ -24,6 +24,14 @@ struct swap_iocb;
#define SHMEM_F_NORESERVE BIT(0)
/* Disallow swapping. */
#define SHMEM_F_LOCKED BIT(1)
+/*
+ * Disallow growing, shrinking, or hole punching in the inode. Combined with
+ * folio pinning, makes sure the inode's mapping stays fixed.
+ *
+ * In some ways similar to F_SEAL_GROW | F_SEAL_SHRINK, but can be removed and
+ * isn't directly visible to userspace.
+ */
+#define SHMEM_F_MAPPING_FROZEN BIT(2)
struct shmem_inode_info {
spinlock_t lock;
@@ -186,6 +194,15 @@ static inline bool shmem_file(struct file *file)
return shmem_mapping(file->f_mapping);
}
+/* Must be called with inode lock taken exclusive. */
+static inline void shmem_freeze(struct inode *inode, bool freeze)
+{
+ if (freeze)
+ SHMEM_I(inode)->flags |= SHMEM_F_MAPPING_FROZEN;
+ else
+ SHMEM_I(inode)->flags &= ~SHMEM_F_MAPPING_FROZEN;
+}
+
/*
* If fallocate(FALLOC_FL_KEEP_SIZE) has been used, there may be pages
* beyond i_size's notion of EOF, which fallocate has committed to reserving:
diff --git a/mm/shmem.c b/mm/shmem.c
index 1d5036dec08a..cb74a5d202ac 100644
--- a/mm/shmem.c
+++ b/mm/shmem.c
@@ -1292,9 +1292,13 @@ static int shmem_setattr(struct mnt_idmap *idmap,
loff_t newsize = attr->ia_size;
/* protected by i_rwsem */
- if ((newsize < oldsize && (info->seals & F_SEAL_SHRINK)) ||
- (newsize > oldsize && (info->seals & F_SEAL_GROW)))
- return -EPERM;
+ if (newsize != oldsize) {
+ if (info->flags & SHMEM_F_MAPPING_FROZEN)
+ return -EPERM;
+ if ((newsize < oldsize && (info->seals & F_SEAL_SHRINK)) ||
+ (newsize > oldsize && (info->seals & F_SEAL_GROW)))
+ return -EPERM;
+ }
if (newsize != oldsize) {
error = shmem_reacct_size(SHMEM_I(inode)->flags,
@@ -3289,6 +3293,10 @@ shmem_write_begin(const struct kiocb *iocb, struct address_space *mapping,
return -EPERM;
}
+ if (unlikely((info->flags & SHMEM_F_MAPPING_FROZEN) &&
+ pos + len > inode->i_size))
+ return -EPERM;
+
ret = shmem_get_folio(inode, index, pos + len, &folio, SGP_WRITE);
if (ret)
return ret;
@@ -3662,6 +3670,11 @@ static long shmem_fallocate(struct file *file, int mode, loff_t offset,
inode_lock(inode);
+ if (info->flags & SHMEM_F_MAPPING_FROZEN) {
+ error = -EPERM;
+ goto out;
+ }
+
if (mode & FALLOC_FL_PUNCH_HOLE) {
struct address_space *mapping = file->f_mapping;
loff_t unmap_start = round_up(offset, PAGE_SIZE);
--
2.52.0.rc2.455.g230fcf2819-goog
next prev parent reply other threads:[~2025-11-22 22:24 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-22 22:23 [PATCH v7 00/22] Live Update Orchestrator Pasha Tatashin
2025-11-22 22:23 ` [PATCH v7 01/22] liveupdate: luo_core: " Pasha Tatashin
2025-11-23 11:12 ` Mike Rapoport
2025-11-23 12:15 ` Pasha Tatashin
2025-11-24 5:07 ` Mike Rapoport
2025-11-24 20:43 ` Pasha Tatashin
2025-11-22 22:23 ` [PATCH v7 02/22] liveupdate: luo_core: integrate with KHO Pasha Tatashin
2025-11-23 11:27 ` Mike Rapoport
2025-11-23 12:03 ` Pasha Tatashin
2025-11-23 14:16 ` Mike Rapoport
2025-11-23 18:23 ` Pasha Tatashin
2025-11-25 13:08 ` Mike Rapoport
2025-11-25 13:59 ` Pasha Tatashin
2025-11-24 14:21 ` Pratyush Yadav
2025-11-25 16:09 ` Pasha Tatashin
2025-11-22 22:23 ` [PATCH v7 03/22] kexec: call liveupdate_reboot() before kexec Pasha Tatashin
2025-11-22 22:23 ` [PATCH v7 04/22] liveupdate: luo_session: add sessions support Pasha Tatashin
2025-11-23 14:16 ` Mike Rapoport
2025-11-23 19:07 ` Pasha Tatashin
2025-11-24 14:57 ` Pratyush Yadav
2025-11-22 22:23 ` [PATCH v7 05/22] liveupdate: luo_core: add user interface Pasha Tatashin
2025-11-23 14:19 ` Mike Rapoport
2025-11-23 19:25 ` Pasha Tatashin
2025-11-24 15:11 ` Pratyush Yadav
2025-11-22 22:23 ` [PATCH v7 06/22] liveupdate: luo_file: implement file systems callbacks Pasha Tatashin
2025-11-24 8:18 ` Mike Rapoport
2025-11-25 15:13 ` Pasha Tatashin
2025-11-24 15:44 ` Pratyush Yadav
2025-11-24 15:47 ` Pratyush Yadav
2025-11-25 15:17 ` Pasha Tatashin
2025-11-22 22:23 ` [PATCH v7 07/22] liveupdate: luo_session: Add ioctls for file preservation Pasha Tatashin
2025-11-24 5:20 ` Mike Rapoport
2025-11-22 22:23 ` [PATCH v7 08/22] docs: add luo documentation Pasha Tatashin
2025-11-23 16:05 ` Mike Rapoport
2025-11-23 19:29 ` Pasha Tatashin
2025-11-24 15:49 ` Pratyush Yadav
2025-11-22 22:23 ` [PATCH v7 09/22] MAINTAINERS: add liveupdate entry Pasha Tatashin
2025-11-23 15:29 ` Mike Rapoport
2025-11-24 15:18 ` Pratyush Yadav
2025-11-22 22:23 ` [PATCH v7 10/22] mm: shmem: use SHMEM_F_* flags instead of VM_* flags Pasha Tatashin
2025-11-22 22:23 ` Pasha Tatashin [this message]
2025-11-23 15:29 ` [PATCH v7 11/22] mm: shmem: allow freezing inode mapping Mike Rapoport
2025-11-23 19:43 ` Pasha Tatashin
2025-11-22 22:23 ` [PATCH v7 12/22] mm: shmem: export some functions to internal.h Pasha Tatashin
2025-11-22 22:23 ` [PATCH v7 13/22] liveupdate: luo_file: add private argument to store runtime state Pasha Tatashin
2025-11-22 22:23 ` [PATCH v7 14/22] mm: memfd_luo: allow preserving memfd Pasha Tatashin
2025-11-23 15:47 ` Mike Rapoport
2025-11-24 3:13 ` Pasha Tatashin
2025-11-22 22:23 ` [PATCH v7 15/22] docs: add documentation for memfd preservation via LUO Pasha Tatashin
2025-11-23 16:07 ` Mike Rapoport
2025-11-22 22:23 ` [PATCH v7 16/22] selftests/liveupdate: Add userspace API selftests Pasha Tatashin
2025-11-24 5:24 ` Mike Rapoport
2025-11-24 15:56 ` Pratyush Yadav
2025-11-22 22:23 ` [PATCH v7 17/22] selftests/liveupdate: Add kexec-based selftest for Pasha Tatashin
2025-11-24 5:29 ` Mike Rapoport
2025-11-22 22:23 ` [PATCH v7 18/22] selftests/liveupdate: Add kexec test for multiple and empty sessions Pasha Tatashin
2025-11-24 5:30 ` Mike Rapoport
2025-11-22 22:23 ` [PATCH v7 19/22] selftests/liveupdate: add test infrastructure and scripts Pasha Tatashin
2025-11-24 7:54 ` Mike Rapoport
2025-11-25 18:42 ` Pasha Tatashin
2025-11-22 22:23 ` [PATCH v7 20/22] liveupdate: luo_file: Add internal APIs for file preservation Pasha Tatashin
2025-11-22 22:23 ` [PATCH v7 21/22] liveupdate: luo_flb: Introduce File-Lifecycle-Bound global state Pasha Tatashin
2025-11-24 23:45 ` David Matlack
2025-11-25 17:10 ` Pasha Tatashin
2025-11-22 22:23 ` [PATCH v7 22/22] tests/liveupdate: Add in-kernel liveupdate test Pasha Tatashin
2025-11-22 22:44 ` [PATCH v7 00/22] Live Update Orchestrator Andrew Morton
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=20251122222351.1059049-12-pasha.tatashin@soleen.com \
--to=pasha.tatashin@soleen.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=ajayachandra@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=aleksander.lobakin@intel.com \
--cc=aliceryhl@google.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=anna.schumaker@oracle.com \
--cc=axboe@kernel.dk \
--cc=bartosz.golaszewski@linaro.org \
--cc=bhelgaas@google.com \
--cc=bp@alien8.de \
--cc=brauner@kernel.org \
--cc=chenridong@huawei.com \
--cc=chrisl@kernel.org \
--cc=corbet@lwn.net \
--cc=cw00.choi@samsung.com \
--cc=dakr@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=david@redhat.com \
--cc=djeffery@redhat.com \
--cc=dmatlack@google.com \
--cc=graf@amazon.com \
--cc=gregkh@linuxfoundation.org \
--cc=hannes@cmpxchg.org \
--cc=hpa@zytor.com \
--cc=hughd@google.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=ira.weiny@intel.com \
--cc=jannh@google.com \
--cc=jasonmiu@google.com \
--cc=jgg@nvidia.com \
--cc=joel.granados@kernel.org \
--cc=kanie@linux.alibaba.com \
--cc=lennart@poettering.net \
--cc=leon@kernel.org \
--cc=leonro@nvidia.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux@weissschuh.net \
--cc=lukas@wunner.de \
--cc=mark.rutland@arm.com \
--cc=masahiroy@kernel.org \
--cc=mingo@redhat.com \
--cc=mmaurer@google.com \
--cc=myungjoo.ham@samsung.com \
--cc=ojeda@kernel.org \
--cc=parav@nvidia.com \
--cc=pratyush@kernel.org \
--cc=ptyadav@amazon.de \
--cc=quic_zijuhu@quicinc.com \
--cc=rafael@kernel.org \
--cc=rdunlap@infradead.org \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=rostedt@goodmis.org \
--cc=rppt@kernel.org \
--cc=saeedm@nvidia.com \
--cc=skhawaja@google.com \
--cc=song@kernel.org \
--cc=stuart.w.hayes@gmail.com \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=vincent.guittot@linaro.org \
--cc=wagi@kernel.org \
--cc=witu@nvidia.com \
--cc=x86@kernel.org \
--cc=yesanishhere@gmail.com \
--cc=yoann.congal@smile.fr \
/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