From: Josh Poimboeuf <jpoimboe@kernel.org>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: live-patching@vger.kernel.org,
Nicholas Piggin <npiggin@gmail.com>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
Song Liu <song@kernel.org>
Subject: Re: [PATCH 0/2] powerpc: Fix livepatch module re-patching issue
Date: Sun, 5 Feb 2023 08:21:56 -0800 [thread overview]
Message-ID: <20230205162156.zganuowqio4kva6o@treble> (raw)
In-Reply-To: <87357ley7f.fsf@mpe.ellerman.id.au>
On Sun, Feb 05, 2023 at 11:46:12AM +1100, Michael Ellerman wrote:
> Josh Poimboeuf <jpoimboe@kernel.org> writes:
> > On Tue, Jan 24, 2023 at 07:38:03PM -0800, Josh Poimboeuf wrote:
> >> Fix a livepatch bug seen when reloading a patched module.
> >>
> >> This is the powerpc counterpart to Song Liu's fix for a similar issue on
> >> x86:
> >>
> >> https://lkml.kernel.org/lkml/20230121004945.697003-2-song@kernel.org
> >>
> >> Josh Poimboeuf (2):
> >> powerpc/module_64: Improve restore_r2() return semantics
> >> powerpc/module_64: Fix "expected nop" error on module re-patching
> >>
> >> arch/powerpc/kernel/module_64.c | 29 ++++++++++++++++++-----------
> >> 1 file changed, 18 insertions(+), 11 deletions(-)
> >
> > Hi Michael,
> >
> > Ping? Any objections to this?
> >
> > The x86 counterpart to this is queued for 6.3, it would be nice if this
> > also landed. We could take it through the livepatch tree if needed.
>
> It's in my next since about a week. Sorry I forgot to send the
> "accepted" emails (which I still don't have automated :/ ).
>
> 337251c7114e1 ("powerpc/module_64: Fix "expected nop" error on module re-patching")
Ah, I didn't think to look in -next. Thanks!
--
Josh
next prev parent reply other threads:[~2023-02-05 16:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-25 3:38 [PATCH 0/2] powerpc: Fix livepatch module re-patching issue Josh Poimboeuf
2023-01-25 3:38 ` [PATCH 1/2] powerpc/module_64: Improve restore_r2() return semantics Josh Poimboeuf
2023-01-25 5:53 ` Song Liu
2023-01-25 13:24 ` Petr Mladek
2023-01-27 12:38 ` Miroslav Benes
2023-01-25 3:38 ` [PATCH 2/2] powerpc/module_64: Fix "expected nop" error on module re-patching Josh Poimboeuf
2023-01-25 6:09 ` Song Liu
2023-01-25 16:46 ` Josh Poimboeuf
2023-01-25 17:36 ` Song Liu
2023-01-25 18:53 ` Josh Poimboeuf
2023-01-25 18:58 ` Song Liu
2023-01-25 13:31 ` Petr Mladek
2023-01-27 12:50 ` Miroslav Benes
2023-01-27 13:48 ` [PATCH 0/2] powerpc: Fix livepatch module re-patching issue Joe Lawrence
2023-02-04 17:23 ` Josh Poimboeuf
2023-02-05 0:46 ` Michael Ellerman
2023-02-05 16:21 ` Josh Poimboeuf [this message]
2023-02-05 0:46 ` Michael Ellerman
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=20230205162156.zganuowqio4kva6o@treble \
--to=jpoimboe@kernel.org \
--cc=christophe.leroy@csgroup.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=live-patching@vger.kernel.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).