From: luca.boccassi@gmail.com
To: kexec@lists.infradead.org
Cc: linux-mm@kvack.org, pasha.tatashin@soleen.com,
pratyush@kernel.org, linux-kernel@vger.kernel.org,
Luca Boccassi <luca.boccassi@gmail.com>
Subject: [PATCH] liveupdate: document systemd support
Date: Tue, 19 May 2026 16:28:39 +0100 [thread overview]
Message-ID: <20260519152957.548119-1-luca.boccassi@gmail.com> (raw)
From: Luca Boccassi <luca.boccassi@gmail.com>
systemd v261 will add native support for LUO via the file descriptor
store mechanism. Add a brief paragraph in the LUO userspace documentation
page to inform users.
Signed-off-by: Luca Boccassi <luca.boccassi@gmail.com>
---
NOTE: the external links will mention LUO after the next release is
published, which should happen within ~4 weeks
Documentation/userspace-api/liveupdate.rst | 23 ++++++++++++++++++++++
1 file changed, 23 insertions(+)
diff --git a/Documentation/userspace-api/liveupdate.rst b/Documentation/userspace-api/liveupdate.rst
index 41c0473e4f16..f6efc32fb40b 100644
--- a/Documentation/userspace-api/liveupdate.rst
+++ b/Documentation/userspace-api/liveupdate.rst
@@ -14,6 +14,29 @@ ioctl uAPI
===========
.. kernel-doc:: include/uapi/linux/liveupdate.h
+Userspace Integration
+=====================
+
+systemd (since version v261) uses LUO to preserve its per-service file
+descriptor store across a kexec-based live update. Services opt in by setting
+``FileDescriptorStoreMax=`` and ``FileDescriptorStorePreserve=`` in their unit,
+and push file descriptors with a name into the store via
+``sd_pid_notify_with_fds(... "FDSTORE=1\nFDNAME=foo")``.
+
+Services may also create their own LUO sessions (via ``/dev/liveupdate``) and
+push the resulting session fds into their file descriptor store like any other
+fd. systemd detects such session fds and handles them accordingly, and
+hands the re-retrieved session fd back to the service after kexec, using the
+existing file descriptor store service interface.
+
+For details, see:
+
+- `File Descriptor Store <https://systemd.io/FILE_DESCRIPTOR_STORE/>`_
+- `systemd.service(5) FileDescriptorStorePreserve=
+ <https://www.freedesktop.org/software/systemd/man/latest/systemd.service.html#FileDescriptorStorePreserve=>`_
+- `sd_pid_notify_with_fds(3)
+ <https://www.freedesktop.org/software/systemd/man/latest/sd_pid_notify_with_fds.html>`_
+
See Also
========
--
2.47.3
next reply other threads:[~2026-05-19 15:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-19 15:28 luca.boccassi [this message]
2026-05-21 15:25 ` [PATCH] liveupdate: document systemd support Pratyush Yadav
2026-05-21 18:00 ` Pasha Tatashin
2026-05-21 17:57 ` Pasha Tatashin
2026-05-21 18:03 ` Pasha Tatashin
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=20260519152957.548119-1-luca.boccassi@gmail.com \
--to=luca.boccassi@gmail.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pasha.tatashin@soleen.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox