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: [RFC PATCH 0/6] livepatch: Introduce replace set support
Date: Tue, 26 May 2026 15:13:04 +0200 [thread overview]
Message-ID: <ahWcYIFs408vuvGP@pathway.suse.cz> (raw)
In-Reply-To: <20260513143321.26185-1-laoar.shao@gmail.com>
On Wed 2026-05-13 22:33:15, Yafang Shao wrote:
> We previously proposed a BPF+livepatch method to enable rapid
> experimentation with new kernel features without interrupting production
> workloads:
>
> https://lore.kernel.org/live-patching/20260402092607.96430-1-laoar.shao@gmail.com/
>
> In the resulting discussion, Song and Petr suggested adding a "replace set"
> to support scenarios where specific livepatches can be selectively replaced
> or skipped.
>
> - Patch #1:
> Adds replace set support for livepatch functions.
>
> - Patch #2~#5:
> Derived from Petr's original patchset:
>
> https://lore.kernel.org/all/20250115082431.5550-3-pmladek@suse.com/
>
> All the selftests are not included in this RFC.
> Note: Due to a significant refactor in Patch #5, I have omitted Petr's
> Signed-off-by for that specific patch. Please let me know if this is not
> the preferred approach.
I am not going to review these patches in this round. They are based
on an outdated RFC. I guess that they do not handle feedback against
the RFC. Also they would require massive changes in the selftests.
Note that I have already done most of the work, see
https://github.com/pmladek/linux/tree/klp-state-transfer-v1-iter12
It requires rebasing on top of last linus tree and some
clean up.
I still hope that I will be able to work on it rather sooner
than later.
> - Patch #6:
> Adds replace set support for the shadow variable API.
Best Regards,
Petr
prev parent reply other threads:[~2026-05-26 13:13 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-13 14:33 [RFC PATCH 0/6] livepatch: Introduce replace set support Yafang Shao
2026-05-13 14:33 ` [RFC PATCH 1/6] livepatch: Support scoped atomic replace using replace set Yafang Shao
2026-05-14 20:54 ` sashiko-bot
2026-05-17 13:32 ` Yafang Shao
2026-05-18 21:25 ` Song Liu
2026-05-26 10:35 ` Petr Mladek
2026-05-26 18:27 ` Song Liu
2026-05-27 2:17 ` Yafang Shao
2026-05-26 12:52 ` Petr Mladek
2026-05-27 2:37 ` Yafang Shao
2026-05-13 14:33 ` [RFC PATCH 2/6] livepatch: Add callbacks for introducing and removing states Yafang Shao
2026-05-13 14:33 ` [RFC PATCH 3/6] livepatch: Allow to handle lifetime of shadow variables using the livepatch state Yafang Shao
2026-05-14 22:07 ` sashiko-bot
2026-05-18 3:24 ` [PATCH] " Yafang Shao
2026-05-13 14:33 ` [RFC PATCH 4/6] livepatch: Remove "data" from struct klp_state Yafang Shao
2026-05-14 22:22 ` sashiko-bot
2026-05-13 14:33 ` [RFC PATCH 5/6] livepatch: Remove obsolete per-object callbacks Yafang Shao
2026-05-14 22:40 ` sashiko-bot
2026-05-19 6:46 ` Yafang Shao
2026-05-13 14:33 ` [RFC PATCH 6/6] livepatch: Support replace_set in shadow variable API Yafang Shao
2026-05-14 23:01 ` sashiko-bot
2026-05-19 6:56 ` Yafang Shao
2026-05-26 13:04 ` Petr Mladek
2026-05-26 13:13 ` 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=ahWcYIFs408vuvGP@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox