From: Petr Mladek <pmladek@suse.com>
To: Song Liu <song@kernel.org>
Cc: Yafang Shao <laoar.shao@gmail.com>,
jpoimboe@kernel.org, jikos@kernel.org, mbenes@suse.cz,
joe.lawrence@redhat.com, live-patching@vger.kernel.org
Subject: Re: [PATCH v9 0/9] livepatch: Add support for scoped atomic replace
Date: Fri, 25 Sep 2026 09:49:32 +0200 [thread overview]
Message-ID: <arYnjJxU_JecIrZq@pathway.suse.cz> (raw)
In-Reply-To: <CAPhsuW5+j8ff0h1ty-vOiAWUnUOcJ0UQhUqvJRVSMrVH9WqbZA@mail.gmail.com>
On Thu 2026-09-24 13:56:32, Song Liu wrote:
> Hi folks,
>
> Do we have pending comments/changes for this set? If not, can we land this
> soon, so that it can go upstream in the upcoming merge window?
I still have to review this last version. It is getting on top
of my TODO list but...
Anyway, my main concern is breaking the backward compatibility.
I assumed that we would discuss this during the micro conference
at Plumbers first.
Best Regards,
Petr
> Thanks,
> Song
>
> On Sat, Sep 12, 2026 at 7:43 PM Yafang Shao <laoar.shao@gmail.com> wrote:
> >
> > Atomic replacement is currently all-or-nothing: a livepatch with
> > "replace" set either atomically replaces all previously installed
> > livepatches, or - with "replace" disabled - it replaces none. There
> > is no way to atomically replace only a selected set of livepatches
> > while keeping the rest running untouched.
> >
> > 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 that it should be
> > possible to selectively replace or skip individual livepatches.
> >
> > This patchset introduces a more flexible model using two new fields in
> > struct klp_patch:
> [...]
next prev parent reply other threads:[~2026-09-25 7:49 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-13 2:42 [PATCH v9 0/9] livepatch: Add support for scoped atomic replace Yafang Shao
2026-09-13 2:42 ` [PATCH v9 1/9] selftests/livepatch: Clarify test module file names Yafang Shao
2026-09-25 8:54 ` Miroslav Benes
2026-09-13 2:42 ` [PATCH v9 2/9] selftests/livepatch: Adapt atomic replace tests to provides/obsoletes Yafang Shao
2026-09-25 8:54 ` Miroslav Benes
2026-09-28 2:55 ` Yafang Shao
2026-09-29 8:42 ` Miroslav Benes
2026-09-29 9:25 ` Yafang Shao
2026-09-13 2:42 ` [PATCH v9 3/9] livepatch: Make klp_find_func() non static Yafang Shao
2026-09-13 2:42 ` [PATCH v9 4/9] livepatch: Call klp_init_patch_early() earlier Yafang Shao
2026-09-13 2:55 ` sashiko-bot
2026-09-13 2:57 ` Yafang Shao
2026-09-13 2:42 ` [PATCH v9 5/9] livepatch: Implement provides and obsoletes for scoped atomic replace Yafang Shao
2026-09-25 11:59 ` Miroslav Benes
2026-09-28 3:09 ` Yafang Shao
2026-09-29 8:44 ` Miroslav Benes
2026-09-13 2:42 ` [PATCH v9 6/9] livepatch: Deprecate stack_order Yafang Shao
2026-09-13 2:48 ` sashiko-bot
2026-09-13 2:55 ` Yafang Shao
2026-09-25 13:00 ` Miroslav Benes
2026-09-13 2:42 ` [PATCH v9 7/9] selftests/livepatch: Add provides/obsoletes test scenarios Yafang Shao
2026-09-25 12:57 ` Miroslav Benes
2026-09-28 3:10 ` Yafang Shao
2026-09-13 2:42 ` [PATCH v9 8/9] selftests/livepatch: Add state test for provides/obsoletes Yafang Shao
2026-09-13 2:42 ` [PATCH v9 9/9] selftests/livepatch: Add function " Yafang Shao
2026-09-24 20:56 ` [PATCH v9 0/9] livepatch: Add support for scoped atomic replace Song Liu
2026-09-25 7:49 ` Petr Mladek [this message]
2026-09-28 2:32 ` 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=arYnjJxU_JecIrZq@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