Re: [PATCH v2 0/2] ivepatch: Fix several bugs found during replace set implementation

On Thu, Aug 20, 2026 at 11:40 PM Josh Poimboeuf [off-list ref] wrote:

On Wed, Aug 19, 2026 at 12:24:31PM +0200, Petr Mladek wrote:

quoted

On Sun 2026-08-16 17:04:40, Yafang Shao wrote:

quoted

These fixes were found while implementing the replace set series [0].
They are independent of that series and can be applied separately.

Link: https://lore.kernel.org/live-patching/20260809091954.22930-1-laoar.shao@gmail.com (local) [0]

Changes:
v1->v2:
- minor improvements and acked-by (Song)
- fix issues reported by sashiko

v1: https://lore.kernel.org/live-patching/20260813030408.9761-1-laoar.shao@gmail.com/ (local)

Yafang Shao (2):
  livepatch: Fix wrong index in funcs cleanup error path

This patch is against scripts/livepatch/init.c which is part of
klp-build framework. The klp-build-related changes usually
go via the "tip" tree by Josh.

quoted

  livepatch: Fix UAF of unregistered patch kobjects

This patch is against the kernel/livepatch/* code. These changes
usually go via the "livepatching" tree by me.

Honestly, I am not sure how to handle this situation.
Josh?

The scripts/livepatch changes have tended to be tied to objtool, which
is why they have gone through the tip tree.

I'm open to suggestions or ideas.  We could possibly rename or move that
scripts/livepatch directory (scripts/klp-build/?  tools/objtool/klp-build/?)
if that makes the boundary less confusing.

Or might there be some other maintainership model or way of splitting up
the files?

My replace set series [0] touches both kernel/livepatch and
scripts/livepatch; I'm not sure whether that would cause conflicts.

Link: https://lore.kernel.org/live-patching/20260809091954.22930-1-laoar.shao@gmail.com/ (local)
[0]

In any case, I'll go ahead and queue up patch 1 for tip for now.

Thanks. I will send a new version excluding patch 1.

-- 
Regards
Yafang