On Wed, Nov 12, 2025 at 03:40:53PM -0500, Pasha Tatashin wrote:

On Wed, Nov 12, 2025 at 3:24 PM Mike Rapoport [off-list ref] wrote:

quoted

On Fri, Nov 07, 2025 at 04:03:20PM -0500, Pasha Tatashin wrote:

quoted

Introduce an in-kernel test module to validate the core logic of the
Live Update Orchestrator's File-Lifecycle-Bound feature. This
provides a low-level, controlled environment to test FLB registration
and callback invocation without requiring userspace interaction or
actual kexec reboots.

The test is enabled by the CONFIG_LIVEUPDATE_TEST Kconfig option.

Signed-off-by: Pasha Tatashin <pasha.tatashin@soleen.com>
---
 kernel/liveupdate/luo_file.c     |   2 +
 kernel/liveupdate/luo_internal.h |   8 ++
 lib/Kconfig.debug                |  23 ++++++
 lib/tests/Makefile               |   1 +
 lib/tests/liveupdate.c           | 130 +++++++++++++++++++++++++++++++
 5 files changed, 164 insertions(+)
 create mode 100644 lib/tests/liveupdate.c

diff --git a/kernel/liveupdate/luo_file.c b/kernel/liveupdate/luo_file.c
index 713069b96278..4c0a75918f3d 100644
--- a/kernel/liveupdate/luo_file.c
+++ b/kernel/liveupdate/luo_file.c

@@ -829,6 +829,8 @@ int liveupdate_register_file_handler(struct liveupdate_file_handler *fh)
      INIT_LIST_HEAD(&fh->flb_list);
      list_add_tail(&fh->list, &luo_file_handler_list);

+     liveupdate_test_register(fh);
+

Do it mean that every flb user will be added here?

No, FLB users will use:

liveupdate_register_flb() from various subsystems. This
liveupdate_test_register() is only to allow kernel test to register
test-FLBs to every single file-handler for in-kernel testing purpose
only.

Why the in kernel test cannot liveupdate_register_flb()?
 

Pasha

-- 
Sincerely yours,
Mike.