From: Petr Mladek <pmladek@suse.com>
To: Harry Hsu <x90613@gmail.com>,
jpoimboe@kernel.org, mbenes@suse.cz, joe.lawrence@redhat.com
Cc: jikos@kernel.org, live-patching@vger.kernel.org,
shuah@kernel.org, song@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/5] livepatch: Fail object initialization on duplicate patched function
Date: Fri, 23 Oct 2026 17:19:52 +0200 [thread overview]
Message-ID: <att7GJXA7hK7Ic64@pathway.suse.cz> (raw)
In-Reply-To: <20260908120325.299649-1-pmladek@suse.com>
On Tue 2026-09-08 14:03:20, Petr Mladek wrote:
> This is v4 of the patch failing object initialization when it patches
> the same underlying function twice through two aliased symbols
> (functions sharing one address) in the same object.
I wonder how to move forward with this patchset. There seems to be
three unresolved problems:
1. How to handle aliased functions when replacing two livepatches
with aliased symbols, aka two NOPs on the same stack [1].
My take: I would fix this later on top of scoped atomic replace.
The aliased symbols should conflict.
2. Fix the low-level __write_relocate_add() to clean its own
mess on failure.
My take: I would fix this a follow up patch.
3. Better describe the purpose of klp_write_object_relocs_limited().
Or clean its own mess a better way (code duplication)?
My take: This requires v5.
[1] https://lore.kernel.org/all/20260908121744.81D641F00A3A@smtp.kernel.org/
[2] https://lore.kernel.org/all/20260908121810.9577A1F00A3A@smtp.kernel.org/
[3] https://lore.kernel.org/all/att3oHvCpVDjDt-h@pathway.suse.cz/
Best Regards,
Petr
next prev parent reply other threads:[~2026-10-23 15:19 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-08 12:03 [PATCH v4 0/5] livepatch: Fail object initialization on duplicate patched function Petr Mladek
2026-09-08 12:03 ` [PATCH v4 1/5] " Petr Mladek
2026-09-08 12:17 ` sashiko-bot
2026-09-08 13:02 ` Petr Mladek
2026-09-18 12:54 ` Miroslav Benes
2026-09-30 14:11 ` [PATCH v4 1/3] " Harry Hsu
2026-10-01 4:32 ` [PATCH v4 1/5] " Harry Hsu
2026-10-23 14:17 ` Petr Mladek
2026-10-27 14:02 ` Miroslav Benes
2026-09-08 12:03 ` [PATCH v4 2/5] selftests/livepatch: Test rejection of aliased symbols in one object Petr Mladek
2026-09-18 13:40 ` Miroslav Benes
2026-09-08 12:03 ` [PATCH v4 3/5] livepatch: Move code for updating livepatch object relocations Petr Mladek
2026-09-18 13:40 ` Miroslav Benes
2026-09-08 12:03 ` [PATCH v4 4/5] livepatch: Clear relocations when klp_apply_object_relocs() fails Petr Mladek
2026-09-08 12:18 ` sashiko-bot
2026-09-08 13:29 ` Petr Mladek
2026-09-18 13:59 ` Miroslav Benes
2026-09-18 14:05 ` Miroslav Benes
2026-10-23 15:05 ` Petr Mladek
2026-10-27 14:21 ` Miroslav Benes
2026-09-08 12:03 ` [PATCH v4 5/5] livepatch: Clean up klp_init_object_loaded() when fails Petr Mladek
2026-09-08 12:25 ` sashiko-bot
2026-09-08 13:32 ` Petr Mladek
2026-09-18 14:07 ` Miroslav Benes
2026-10-23 15:19 ` Petr Mladek [this message]
2026-10-28 16:46 ` [PATCH v4 0/5] livepatch: Fail object initialization on duplicate patched function Harry Hsu
2026-10-30 9:15 ` Petr Mladek
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=att7GJXA7hK7Ic64@pathway.suse.cz \
--to=pmladek@suse.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=shuah@kernel.org \
--cc=song@kernel.org \
--cc=x90613@gmail.com \
/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.