From: Petr Mladek <pmladek@suse.com>
To: Yafang Shao <laoar.shao@gmail.com>
Cc: jpoimboe@kernel.org, jikos@kernel.org, mbenes@suse.cz,
joe.lawrence@redhat.com, song@kernel.org,
live-patching@vger.kernel.org
Subject: Re: [PATCH v12 9/9] selftests/livepatch: Add function test for provides/obsoletes
Date: Thu, 22 Oct 2026 17:59:02 +0200 [thread overview]
Message-ID: <atoyxoxWSVqZvHUE@pathway.suse.cz> (raw)
In-Reply-To: <20261016053708.47089-10-laoar.shao@gmail.com>
On Fri 2026-10-16 13:37:08, Yafang Shao wrote:
> Livepatches with different provides ids must not modify the same
> function, unless they share the same provides id or the second
> livepatch obsoletes the first one.
>
> Add test scenarios that verify this rule on the combination of
> patched functions and provides ids.
>
> These tests are skipped on kernels that still support the legacy
> "replace" attribute.
>
> Suggested-by: Petr Mladek <pmladek@suse.com>
> Signed-off-by: Yafang Shao <laoar.shao@gmail.com>
Looks good to me and passes the selftests:
Reviewed-by: Petr Mladek <pmladek@suse.com>
Tested-by: Petr Mladek <pmladek@suse.com>
Best Regards,
Petr
prev parent reply other threads:[~2026-10-22 15:59 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 5:36 [PATCH v12 0/9] livepatch: Add support for scoped atomic replace Yafang Shao
2026-10-16 5:37 ` [PATCH v12 1/9] selftests/livepatch: Clarify test module file names Yafang Shao
2026-10-16 5:37 ` [PATCH v12 2/9] selftests/livepatch: Adapt atomic replace tests to provides/obsoletes Yafang Shao
2026-10-16 5:37 ` [PATCH v12 3/9] livepatch: Make klp_find_func() non static Yafang Shao
2026-10-16 5:37 ` [PATCH v12 4/9] livepatch: Call klp_init_patch_early() earlier Yafang Shao
2026-10-16 5:47 ` sashiko-bot
2026-10-16 7:49 ` Yafang Shao
2026-10-16 5:37 ` [PATCH v12 5/9] livepatch: Implement provides and obsoletes for scoped atomic replace Yafang Shao
2026-10-16 5:48 ` sashiko-bot
2026-10-16 7:46 ` Yafang Shao
2026-10-21 15:26 ` Petr Mladek
2026-10-22 5:47 ` Yafang Shao
2026-10-23 9:58 ` temporary broken selftest: was: " Petr Mladek
2026-10-25 7:57 ` Yafang Shao
2026-10-16 5:37 ` [PATCH v12 6/9] livepatch: Deprecate stack_order Yafang Shao
2026-10-22 15:10 ` Petr Mladek
2026-10-16 5:37 ` [PATCH v12 7/9] selftests/livepatch: Add provides/obsoletes test scenarios Yafang Shao
2026-10-23 9:58 ` Petr Mladek
2026-10-16 5:37 ` [PATCH v12 8/9] selftests/livepatch: Add state test for provides/obsoletes Yafang Shao
2026-10-23 9:58 ` Petr Mladek
2026-10-25 8:18 ` Yafang Shao
2026-10-16 5:37 ` [PATCH v12 9/9] selftests/livepatch: Add function " Yafang Shao
2026-10-22 15:59 ` Petr Mladek [this message]
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=atoyxoxWSVqZvHUE@pathway.suse.cz \
--to=pmladek@suse.com \
--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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.