All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell Currey <ruscur@russell.cc>
To: Joe Lawrence <joe.lawrence@redhat.com>, linuxppc-dev@lists.ozlabs.org
Cc: jniethe5@gmail.com, naveen.n.rao@linux.vnet.ibm.com,
	mpe@ellerman.id.au, christophe.leroy@csgroup.eu,
	live-patching@vger.kernel.org
Subject: Re: [PATCH] powerpc/module_64: Fix livepatching for RO modules
Date: Wed, 08 Dec 2021 11:51:27 +1000	[thread overview]
Message-ID: <25d35b916e87ed7a71ebc6528259e2f0ed390cb2.camel@russell.cc> (raw)
In-Reply-To: <d9d9ef2d-4aaa-7d8b-d15e-0452a355c5cf@redhat.com>

On Tue, 2021-12-07 at 09:44 -0500, Joe Lawrence wrote:
> On 11/23/21 3:15 AM, Russell Currey wrote:
> 
> [[ cc += livepatching list ]]
> 
> Hi Russell,
> 
> Thanks for writing a minimal fix for stable / backporting.  As I
> mentioned on the github issue [1], this avoided the crashes I
> reported
> here and over on kpatch github [2].  I wasn't sure if this is the
> final
> version for stable, but feel free to add my:
> 
> Tested-by: Joe Lawrence <joe.lawrence@redhat.com>

Thanks Joe, as per the discussions on GitHub I think we're fine to use
this patch for a fix for stable (unless there's new issues found or
additional community feedback etc).

> 
> [1] https://github.com/linuxppc/issues/issues/375
> [2] https://github.com/dynup/kpatch/issues/1228
> 


WARNING: multiple messages have this Message-ID (diff)
From: Russell Currey <ruscur@russell.cc>
To: Joe Lawrence <joe.lawrence@redhat.com>, linuxppc-dev@lists.ozlabs.org
Cc: live-patching@vger.kernel.org, jniethe5@gmail.com,
	naveen.n.rao@linux.vnet.ibm.com
Subject: Re: [PATCH] powerpc/module_64: Fix livepatching for RO modules
Date: Wed, 08 Dec 2021 11:51:27 +1000	[thread overview]
Message-ID: <25d35b916e87ed7a71ebc6528259e2f0ed390cb2.camel@russell.cc> (raw)
In-Reply-To: <d9d9ef2d-4aaa-7d8b-d15e-0452a355c5cf@redhat.com>

On Tue, 2021-12-07 at 09:44 -0500, Joe Lawrence wrote:
> On 11/23/21 3:15 AM, Russell Currey wrote:
> 
> [[ cc += livepatching list ]]
> 
> Hi Russell,
> 
> Thanks for writing a minimal fix for stable / backporting.  As I
> mentioned on the github issue [1], this avoided the crashes I
> reported
> here and over on kpatch github [2].  I wasn't sure if this is the
> final
> version for stable, but feel free to add my:
> 
> Tested-by: Joe Lawrence <joe.lawrence@redhat.com>

Thanks Joe, as per the discussions on GitHub I think we're fine to use
this patch for a fix for stable (unless there's new issues found or
additional community feedback etc).

> 
> [1] https://github.com/linuxppc/issues/issues/375
> [2] https://github.com/dynup/kpatch/issues/1228
> 


  reply	other threads:[~2021-12-08  1:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-23  8:15 [PATCH] powerpc/module_64: Fix livepatching for RO modules Russell Currey
2021-12-07 14:44 ` Joe Lawrence
2021-12-07 14:44   ` Joe Lawrence
2021-12-08  1:51   ` Russell Currey [this message]
2021-12-08  1:51     ` Russell Currey
2021-12-09  7:00     ` Michael Ellerman
2021-12-09  7:00       ` Michael Ellerman
2021-12-10  3:08       ` Joe Lawrence
2021-12-10  3:08         ` Joe Lawrence
2021-12-15  0:51 ` 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=25d35b916e87ed7a71ebc6528259e2f0ed390cb2.camel@russell.cc \
    --to=ruscur@russell.cc \
    --cc=christophe.leroy@csgroup.eu \
    --cc=jniethe5@gmail.com \
    --cc=joe.lawrence@redhat.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=live-patching@vger.kernel.org \
    --cc=mpe@ellerman.id.au \
    --cc=naveen.n.rao@linux.vnet.ibm.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.