From: Pasha Tatashin <pasha.tatashin@soleen.com>
To: linux-kselftest@vger.kernel.org, rppt@kernel.org,
shuah@kernel.org, akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, pasha.tatashin@soleen.com,
dmatlack@google.com, pratyush@kernel.org, skhawaja@google.com
Subject: [PATCH v3 0/2] liveupdate: prevent double preservation
Date: Wed, 25 Mar 2026 18:20:24 +0000 [thread overview]
Message-ID: <20260325182026.467307-1-pasha.tatashin@soleen.com> (raw)
Currently, LUO does not prevent the same file from being preserved twice
across different active sessions.
Because LUO preserves files of absolutely different types: memfd, and
upcoming vfiofd [1], iommufd [2], guestmefd (and possible kvmfd/cpufd).
There is no common private data or guarantee on how to prevent that the
same file is not preserved twice beside using inode or some slower and
expensive method like hashtables.
[1] https://lore.kernel.org/all/20260129212510.967611-1-dmatlack@google.com
[2] https://lore.kernel.org/all/20260203220948.2176157-1-skhawaja@google.com
Changelog:
v3:
- Renamed luo_preserved_files_xa to luo_preserved_files (Mike)
- Added xa inserts during restoration, so a file that is not yet finished is
not preserved at the same time. (Sashiko)
v2:
- Because inodes of preserved files can be shared, we cannot rely on a
flag in the inode. Therefore, use an xarray to prevent preserving
duplicated files.
Pasha Tatashin (2):
liveupdate: prevent double management of files
selftests: liveupdate: add test for double preservation
kernel/liveupdate/luo_file.c | 26 ++++++++++--
.../testing/selftests/liveupdate/liveupdate.c | 41 +++++++++++++++++++
2 files changed, 64 insertions(+), 3 deletions(-)
base-commit: 785f0eb2f85decbe7c1ef9ae922931f0194ffc2e
--
2.43.0
next reply other threads:[~2026-03-25 18:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-25 18:20 Pasha Tatashin [this message]
2026-03-25 18:20 ` [PATCH v3 1/2] liveupdate: prevent double management of files Pasha Tatashin
2026-03-25 18:56 ` Mike Rapoport
2026-03-25 20:20 ` Pratyush Yadav
2026-03-25 20:33 ` David Matlack
2026-03-25 21:08 ` Pasha Tatashin
2026-03-25 21:35 ` Pasha Tatashin
2026-03-26 9:04 ` Mike Rapoport
2026-03-25 18:20 ` [PATCH v3 2/2] selftests: liveupdate: add test for double preservation Pasha Tatashin
2026-03-25 23:14 ` [PATCH v3 0/2] liveupdate: prevent " 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=20260325182026.467307-1-pasha.tatashin@soleen.com \
--to=pasha.tatashin@soleen.com \
--cc=akpm@linux-foundation.org \
--cc=dmatlack@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pratyush@kernel.org \
--cc=rppt@kernel.org \
--cc=shuah@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