From: Joe Lawrence <joe.lawrence@redhat.com>
To: Russell Currey <ruscur@russell.cc>,
live-patching@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Cc: Josh Poimboeuf <jpoimboe@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Jessica Yu <jeyu@kernel.org>, Jordan Niethe <jniethe5@gmail.com>,
Christophe Leroy <christophe.leroy@csgroup.eu>
Subject: Re: ppc64le STRICT_MODULE_RWX and livepatch apply_relocate_add() crashes
Date: Mon, 1 Nov 2021 09:48:35 -0400 [thread overview]
Message-ID: <f8a96ac1-fda3-92da-cf27-0992a43a2f3f@redhat.com> (raw)
In-Reply-To: <7ee0c84650617e6307b29674dd0a12c7258417cf.camel@russell.cc>
On 11/1/21 5:20 AM, Russell Currey wrote:
> I'm looking into this now, will update when there's progress. I
> personally wasn't aware but Jordan flagged this as an issue back in
> August [0]. Are the selftests in the klp-convert tree sufficient for
> testing? I'm not especially familiar with livepatching & haven't used
> the userspace tools.
>
Hi Russell, thanks for taking a look.
Testing with that klp-convert tree is probably the quickest and easiest
way to verify the late relocations.
I'm happy to setup and test additional tools (ie, kpatch-build) with any
potential changes as I know they take longer to config and run.
Thanks,
--
Joe
next prev parent reply other threads:[~2021-11-01 13:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-01 2:43 ppc64le STRICT_MODULE_RWX and livepatch apply_relocate_add() crashes Joe Lawrence
2021-11-01 9:20 ` Russell Currey
2021-11-01 13:48 ` Joe Lawrence [this message]
2021-12-13 7:42 ` Christophe Leroy
2021-12-13 14:47 ` Joe Lawrence
2021-12-13 16:36 ` Christophe Leroy
2021-12-13 17:26 ` Joe Lawrence
2021-12-14 12:44 ` Christophe Leroy
2021-12-14 13:00 ` Joe Lawrence
2021-12-14 13:35 ` Christophe Leroy
2021-11-03 21:33 ` Suraj Jitindar Singh
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=f8a96ac1-fda3-92da-cf27-0992a43a2f3f@redhat.com \
--to=joe.lawrence@redhat.com \
--cc=christophe.leroy@csgroup.eu \
--cc=jeyu@kernel.org \
--cc=jniethe5@gmail.com \
--cc=jpoimboe@redhat.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=live-patching@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=ruscur@russell.cc \
/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 NNTP newsgroup(s).