From: "Pablo Hugen" <phugen@redhat.com>
To: "Miroslav Benes" <mbenes@suse.cz>,
"Joe Lawrence" <joe.lawrence@redhat.com>
Cc: "Petr Mladek" <pmladek@suse.com>,
"Pablo Hugen" <phugen@redhat.com>,
<live-patching@vger.kernel.org>,
<linux-kselftest@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<jpoimboe@kernel.org>, <jikos@kernel.org>, <shuah@kernel.org>
Subject: Re: [PATCH] selftests/livepatch: add test for module function patching
Date: Tue, 31 Mar 2026 18:10:16 -0300 [thread overview]
Message-ID: <DHH9XZULMJOP.VB88ZIPXYI4J@redhat.com> (raw)
In-Reply-To: <alpine.LSU.2.21.2603271143310.31210@pobox.suse.cz>
[-- Attachment #1: Type: text/plain, Size: 908 bytes --]
> > Summary:
> >
> > IMHO, this patch is perfectly fine as is if we accept that it will get
> > eventually obsoleted by my patchset (hopefully in a year or two).
> >
> > On the other hand, this patch would deserve some clean up,
> > (helper functions, don't die in the middle of the test) if
> > you planned to work on more tests. It would help to maintain
> > the tests.
> Right, I think this was a good intro patch for Pablo and that the
> revised execution flow would be a great follow on series, if he is
> interested. How about that?
Sure, will take a stab at revising the cleanup flow. And thanks for the ideas.
> > This code is repeated several times. It might be worth creating a
> > helper function in tools/testing/selftests/livepatch/functions.sh.
Makes sense. Will include in the follow-up.
Thanks for the reviews everyone, and thanks Petr for picking it up.
Pablo
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-03-31 21:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-20 20:11 [PATCH] selftests/livepatch: add test for module function patching Pablo Hugen
2026-03-24 14:22 ` Miroslav Benes
2026-03-24 14:45 ` Joe Lawrence
2026-03-25 8:45 ` Miroslav Benes
2026-03-31 20:52 ` Pablo Hugen
2026-03-26 14:34 ` Petr Mladek
2026-03-26 20:41 ` Joe Lawrence
2026-03-27 10:46 ` Miroslav Benes
2026-03-31 21:10 ` Pablo Hugen [this message]
2026-03-30 13:43 ` Petr Mladek
2026-03-30 13:48 ` speaker-test-module: " 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=DHH9XZULMJOP.VB88ZIPXYI4J@redhat.com \
--to=phugen@redhat.com \
--cc=jikos@kernel.org \
--cc=joe.lawrence@redhat.com \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=pmladek@suse.com \
--cc=shuah@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.