From: Harry Hsu <x90613@gmail.com>
To: song@kernel.org
Cc: pmladek@suse.com, jpoimboe@kernel.org, jikos@kernel.org,
mbenes@suse.cz, joe.lawrence@redhat.com,
live-patching@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] livepatch: Reject livepatches with aliased old_func
Date: Mon, 31 Aug 2026 01:51:28 +0800 [thread overview]
Message-ID: <20260830175128.58926-1-x90613@gmail.com> (raw)
In-Reply-To: <CAPhsuW70RpkZ1ciioSjt6qkQePWyeic_L+98d0h-Ao3ze-TmkA@mail.gmail.com>
On Fri, Aug 28, 2026 at 9:17 AM Song Liu <song@kernel.org> wrote:
>
> Acked-by: Song Liu <song@kernel.org>
>
> Can we add a selftest for this case?
Sure, I'll add a selftest for this. I'll send a follow-up patch
within a week that exercises patching two aliased symbols from the
same livepatch object and confirms it's rejected with -EINVAL.
Thanks,
Harry
next prev parent reply other threads:[~2026-08-30 17:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-23 6:07 [PATCH v2] livepatch: Reject livepatches with aliased old_func Harry Hsu
2026-08-23 6:23 ` sashiko-bot
2026-08-27 15:45 ` Petr Mladek
2026-08-28 12:52 ` [PATCH 0/2] livepatch: Clear relocations when klp_init_object_loaded() fails Petr Mladek
2026-08-28 12:52 ` [PATCH 1/2] livepatch: Move code for updating livepatch object relocations Petr Mladek
2026-08-28 17:02 ` Song Liu
2026-08-28 17:41 ` Josh Poimboeuf
2026-08-28 17:52 ` Song Liu
2026-08-28 12:52 ` [PATCH 2/2] livepatch: Clean up klp_init_object_loaded() when fails Petr Mladek
2026-08-28 17:44 ` Song Liu
2026-08-31 8:44 ` Petr Mladek
2026-08-27 14:42 ` [PATCH v2] livepatch: Reject livepatches with aliased old_func Petr Mladek
2026-08-27 22:57 ` Josh Poimboeuf
2026-08-28 9:25 ` Miroslav Benes
2026-08-28 16:17 ` Song Liu
2026-08-30 17:51 ` Harry Hsu [this message]
2026-08-30 17:51 ` Harry Hsu
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=20260830175128.58926-1-x90613@gmail.com \
--to=x90613@gmail.com \
--cc=jikos@kernel.org \
--cc=joe.lawrence@redhat.com \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=pmladek@suse.com \
--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