From: Petr Mladek <pmladek@suse.com>
To: Josh Poimboeuf <jpoimboe@kernel.org>
Cc: jikos@kernel.org, mbenes@suse.cz, joe.lawrence@redhat.com,
song@kernel.org, live-patching@vger.kernel.org,
Yafang Shao <laoar.shao@gmail.com>
Subject: Re: [PATCH v2 0/2] ivepatch: Fix several bugs found during replace set implementation
Date: Fri, 21 Aug 2026 10:51:44 +0200 [thread overview]
Message-ID: <aogRoHC151zl8VxW@pathway.suse.cz> (raw)
In-Reply-To: <aocdq0hr_iQTimG0@jpoimboe>
On Thu 2026-08-20 08:40:40, Josh Poimboeuf wrote:
> On Wed, Aug 19, 2026 at 12:24:31PM +0200, Petr Mladek wrote:
> > On Sun 2026-08-16 17:04:40, Yafang Shao wrote:
> > > 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 [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/
> > >
> > > 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.
> >
> > > 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.
Yup.
> 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.
I like the idea with klp-build name. It might help people to
distinguish the two areas.
> Or might there be some other maintainership model or way of splitting up
> the files?
I guess that we need to keep the core livepatching code and klp-build
stuff separated because klp-build is very tight with objtool and
objtool is tight with arch code, ...
It might help to crate KLP BUILD section in MAINTAINERS.
It would point to the tip tree. You would be the maintainer.
And other livepatch people, including live-patching mailing list,
might stay as reviewers.
> In any case, I'll go ahead and queue up patch 1 for tip for now.
Thanks a lot.
Best Regards,
Petr
prev parent reply other threads:[~2026-08-21 8:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-16 9:04 [PATCH v2 0/2] ivepatch: Fix several bugs found during replace set implementation Yafang Shao
2026-08-16 9:04 ` [PATCH v2 1/2] livepatch: Fix wrong index in funcs cleanup error path Yafang Shao
2026-08-16 9:04 ` [PATCH v2 2/2] livepatch: Fix UAF of unregistered patch kobjects Yafang Shao
2026-08-19 11:18 ` Petr Mladek
2026-08-19 12:37 ` Yafang Shao
2026-08-19 12:59 ` Petr Mladek
2026-08-19 10:24 ` [PATCH v2 0/2] ivepatch: Fix several bugs found during replace set implementation Petr Mladek
2026-08-20 15:40 ` Josh Poimboeuf
2026-08-21 3:14 ` Yafang Shao
2026-08-21 8:51 ` 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=aogRoHC151zl8VxW@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.