From: sashiko-bot@kernel.org
To: jikos@kernel.org, "Yafang Shao" <laoar.shao@gmail.com>,
mbenes@suse.cz, pmladek@suse.com, joe.lawrence@redhat.com,
song@kernel.org, jpoimboe@kernel.org
Cc: live-patching@vger.kernel.org
Subject: Re: [PATCH v10 7/9] selftests/livepatch: Add provides/obsoletes test scenarios
Date: Wed, 30 Sep 2026 03:13:58 +0000 [thread overview]
Message-ID: <20260930031358.8C7611F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260930030323.14396-8-laoar.shao@gmail.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] selftests: comment mismatch in obsoletes test
--
commit b0b3364b7d14143d4a32c2c1ce9eaf4a8c23c322
Author: Yafang Shao <laoar.shao@gmail.com>
selftests/livepatch: Add provides/obsoletes test scenarios
This commit adds test scenarios for the new provides/obsoletes livepatch
mechanism, verifying various replacement semantics. The tests are skipped
on kernels that only support the legacy "replace" attribute.
> diff --git a/tools/testing/selftests/livepatch/test-provides-obsoletes.sh b/tools/testing/selftests/livepatch/test-provides-obsoletes.sh
> new file mode 100755
> index 0000000000000..a1c0ebb9ed44e
> --- /dev/null
> +++ b/tools/testing/selftests/livepatch/test-provides-obsoletes.sh
[ ... ]
> +# - load a livepatch with provides=2 and obsoletes=[1] (cmdline),
> +# then another with provides=1 (meminfo). Although the second patch
[Severity: Low]
Does this block comment swap the module names?
The text says cmdline is loaded with obsoletes=[1] and meminfo is loaded
second. However, as noted later in this same comment block and in the test
implementation below, MOD_MEMINFO is loaded first with obsoletes=1 and
MOD_CMDLINE is loaded second. This is functionally necessary because
test_klp_cmdline_lp.c does not declare an obsoletes module parameter.
> +# does not list provides=2 in its own obsoletes list, it still
> +# replaces the first one, because the obsoletes relationship is
> +# symmetric: the first patch's obsoletes list contains the second
> +# patch's provides id.
> +# - verify the provides sysfs value of the replacing patch
> +# - unload the remaining livepatch
> +#
> +# MOD_MEMINFO(provides=2, obsoletes=[1]) -- loaded first
> +# MOD_CMDLINE(provides=1) -- loaded second, replaces above
> +
> +start_test "symmetric obsoletes replaces"
> +
> +load_lp $MOD_MEMINFO provides=2 obsoletes=1
> +load_lp $MOD_CMDLINE provides=1
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260930030323.14396-1-laoar.shao@gmail.com?part=7
next prev parent reply other threads:[~2026-09-30 3:13 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 3:03 [PATCH v10 0/9] livepatch: Add support for scoped atomic replace Yafang Shao
2026-09-30 3:03 ` [PATCH v10 1/9] selftests/livepatch: Clarify test module file names Yafang Shao
2026-10-01 15:27 ` Petr Mladek
2026-09-30 3:03 ` [PATCH v10 2/9] selftests/livepatch: Adapt atomic replace tests to provides/obsoletes Yafang Shao
2026-10-01 15:57 ` Petr Mladek
2026-10-02 12:01 ` Miroslav Benes
2026-09-30 3:03 ` [PATCH v10 3/9] livepatch: Make klp_find_func() non static Yafang Shao
2026-10-02 14:19 ` Petr Mladek
2026-09-30 3:03 ` [PATCH v10 4/9] livepatch: Call klp_init_patch_early() earlier Yafang Shao
2026-10-02 15:58 ` Petr Mladek
2026-09-30 3:03 ` [PATCH v10 5/9] livepatch: Implement provides and obsoletes for scoped atomic replace Yafang Shao
2026-10-02 12:01 ` Miroslav Benes
2026-10-02 17:06 ` Petr Mladek
2026-10-04 15:46 ` Yafang Shao
2026-10-08 10:30 ` Petr Mladek
2026-10-08 11:04 ` Yafang Shao
2026-10-09 8:33 ` Yafang Shao
2026-09-30 3:03 ` [PATCH v10 6/9] livepatch: Deprecate stack_order Yafang Shao
2026-09-30 3:03 ` [PATCH v10 7/9] selftests/livepatch: Add provides/obsoletes test scenarios Yafang Shao
2026-09-30 3:13 ` sashiko-bot [this message]
2026-09-30 3:29 ` Yafang Shao
2026-10-02 12:27 ` Miroslav Benes
2026-09-30 3:03 ` [PATCH v10 8/9] selftests/livepatch: Add state test for provides/obsoletes Yafang Shao
2026-09-30 3:03 ` [PATCH v10 9/9] selftests/livepatch: Add function " Yafang Shao
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=20260930031358.8C7611F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=jikos@kernel.org \
--cc=joe.lawrence@redhat.com \
--cc=jpoimboe@kernel.org \
--cc=laoar.shao@gmail.com \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=pmladek@suse.com \
--cc=sashiko-reviews@lists.linux.dev \
--cc=song@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