From: Marcos Paulo de Souza <mpdesouza@suse.com>
To: Joe Lawrence <joe.lawrence@redhat.com>
Cc: Josh Poimboeuf <jpoimboe@kernel.org>,
Jiri Kosina <jikos@kernel.org>, Miroslav Benes <mbenes@suse.cz>,
Petr Mladek <pmladek@suse.com>, Shuah Khan <shuah@kernel.org>,
live-patching@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] selftests: livepatch: Test atomic replace against multiple modules
Date: Tue, 04 Jun 2024 17:59:48 -0300 [thread overview]
Message-ID: <d98580bc15fd358a1bdfdbc95b94ca02f97324bc.camel@suse.com> (raw)
In-Reply-To: <Zl9YoIAy+1bEnHCB@redhat.com>
On Tue, 2024-06-04 at 14:10 -0400, Joe Lawrence wrote:
> On Mon, Jun 03, 2024 at 02:26:19PM -0300, Marcos Paulo de Souza
> wrote:
> > Adapt the current test-livepatch.sh script to account the number of
> > applied livepatches and ensure that an atomic replace livepatch
> > disables
> > all previously applied livepatches.
> >
> > Signed-off-by: Marcos Paulo de Souza <mpdesouza@suse.com>
> > ---
> > Changes since v2:
> > * Used variables to stop the name of other livepatches applied to
> > test
> > the atomic replace. (Joe)
> >
> > Changes since v1:
> > * Added checks in the existing test-livepatch.sh instead of
> > creating a
> > new test file. (Joe)
> > * Fixed issues reported by ShellCheck (Joe)
> > ---
> > Changes in v3:
> > - EDITME: describe what is new in this series revision.
> > - EDITME: use bulletpoints and terse descriptions.
> > - Link to v2:
> > https://lore.kernel.org/r/20240525-lp-atomic-replace-v2-1-142199bb65a1@suse.com
> > ---
> > .../testing/selftests/livepatch/test-livepatch.sh | 138
> > +++++++++++++--------
> > 1 file changed, 89 insertions(+), 49 deletions(-)
> >
> > diff --git a/tools/testing/selftests/livepatch/test-livepatch.sh
> > b/tools/testing/selftests/livepatch/test-livepatch.sh
> > index e3455a6b1158..ca770b8c62fc 100755
> > --- a/tools/testing/selftests/livepatch/test-livepatch.sh
> > +++ b/tools/testing/selftests/livepatch/test-livepatch.sh
> >
> > [ ... snip ... ]
> >
> > # - load a livepatch that modifies the output from /proc/cmdline
> > and
> > # verify correct behavior
> > -# - load an atomic replace livepatch and verify that only the
> > second is active
> > -# - remove the first livepatch and verify that the atomic replace
> > livepatch
> > -# is still active
> > +# - load two addtional livepatches and check the number of
> > livepatch modules
>
> nit: s/addtional/additional as Miroslav spotted in v2
>
> Otherwise LGTM,
>
> Acked-by: Joe Lawrence <joe.lawrence@redhat.com>
Thanks Joe! I forgot to address Miroslav's comment... Petr, would you
fix it locally?
Thanks!
>
> --
> Joe
>
next prev parent reply other threads:[~2024-06-04 21:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-03 17:26 [PATCH v3] selftests: livepatch: Test atomic replace against multiple modules Marcos Paulo de Souza
2024-06-03 17:31 ` Marcos Paulo de Souza
2024-06-04 18:10 ` Joe Lawrence
2024-06-04 20:59 ` Marcos Paulo de Souza [this message]
2024-06-07 8:26 ` Miroslav Benes
2024-06-18 8:44 ` Petr Mladek
2024-06-18 9:52 ` 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=d98580bc15fd358a1bdfdbc95b94ca02f97324bc.camel@suse.com \
--to=mpdesouza@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox