From: sashiko-bot@kernel.org
To: "Tarun Sahu" <tarunsahu@google.com>,
loganodell@google.com, alex@shazbot.org, dwmw2@infradead.org,
seanjc@google.com, "Mike Rapoport" <rppt@kernel.org>,
will@kernel.org, pbonzini@redhat.com, jgg@nvidia.com,
"Pasha Tatashin" <pasha.tatashin@soleen.com>,
arnd@arndb.de, "Andrew Morton" <akpm@linux-foundation.org>,
oupton@kernel.org, baolu.lu@linux.intel.com,
"David Matlack" <dmatlack@google.com>,
robin.murphy@arm.com, maz@kernel.org,
"Alexander Graf" <graf@amazon.com>,
joro@8bytes.org, "Bjorn Helgaas" <bhelgaas@google.com>,
kevin.tian@intel.com, "Pratyush Yadav" <pratyush@kernel.org>
Cc: kexec@lists.infradead.org
Subject: Re: [RFC PATCH v3 4/4] liveupdate: Add KUnit test for the feature header helpers
Date: Mon, 26 Oct 2026 17:53:55 +0000 [thread overview]
Message-ID: <sashiko-outbox-185601@kernel.org> (raw)
In-Reply-To: <20261026174217.603114-5-tarunsahu@google.com>
> Add a KUnit test suite in lib/tests/liveupdate_feature_kunit.c covering
> the Live Update feature header declared in include/linux/kho/abi/luo.h.
>
> The suite contains two focused test cases:
> - luo_ser_hdr_set_get_test: verifies DECLARE_LUO_SER_WRAP structure
> sizing, header initialization, payload pointer resolution, and 2-bit
> feature flag setting and retrieval across flags entry boundaries,
> including out-of-range queries.
> - luo_ser_hdr_truth_table_test: verifies luo_ser_hdr_validate against
> all rows of the feature state truth table (absent, optional,
> required, and reserved 0b10 encodings), as well as empty supported
> tables.
>
> Signed-off-by: Tarun Sahu <tarunsahu@google.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261026174217.603114-1-tarunsahu@google.com?part=4
next prev parent reply other threads:[~2026-10-26 17:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-26 17:42 [RFC PATCH v3 0/4] liveupdate: Add feature header for fine-grained ABI compatibility Tarun Sahu
2026-10-26 17:42 ` [RFC PATCH v3 1/4] liveupdate: Remove __packed from LUO and memfd ABI structures Tarun Sahu
2026-10-26 17:53 ` sashiko-bot
2026-10-26 17:42 ` [RFC PATCH v3 2/4] liveupdate: Add feature header for fine-grained ABI compatibility Tarun Sahu
2026-10-26 17:53 ` sashiko-bot
2026-10-26 17:42 ` [RFC PATCH v3 3/4] mm: memfd_luo: Add the feature header Tarun Sahu
2026-10-26 17:53 ` sashiko-bot
2026-10-26 17:42 ` [RFC PATCH v3 4/4] liveupdate: Add KUnit test for the feature header helpers Tarun Sahu
2026-10-26 17:53 ` sashiko-bot [this message]
2026-10-26 18:58 ` [RFC PATCH v3 0/4] liveupdate: Add feature header for fine-grained ABI compatibility tarunsahu
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=sashiko-outbox-185601@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alex@shazbot.org \
--cc=arnd@arndb.de \
--cc=baolu.lu@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=dmatlack@google.com \
--cc=dwmw2@infradead.org \
--cc=graf@amazon.com \
--cc=jgg@nvidia.com \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=kexec@lists.infradead.org \
--cc=loganodell@google.com \
--cc=maz@kernel.org \
--cc=oupton@kernel.org \
--cc=pasha.tatashin@soleen.com \
--cc=pbonzini@redhat.com \
--cc=pratyush@kernel.org \
--cc=robin.murphy@arm.com \
--cc=rppt@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=seanjc@google.com \
--cc=tarunsahu@google.com \
--cc=will@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