From: Christopher Arges <chris.j.arges@canonical.com>
To: Jessica Yu <jeyu@redhat.com>
Cc: Josh Poimboeuf <jpoimboe@redhat.com>,
Miroslav Benes <mbenes@suse.cz>, Petr Mladek <pmladek@suse.com>,
Jiri Kosina <jikos@kernel.org>,
Eugene Shatokhin <eugene.shatokhin@rosalab.ru>,
live-patching@vger.kernel.org, x86@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] Fix issue with alternatives/paravirt patches
Date: Fri, 8 Jul 2016 00:22:22 -0500 [thread overview]
Message-ID: <20160708052222.GA1549@gmail.com> (raw)
In-Reply-To: <1467772500-26092-1-git-send-email-jeyu@redhat.com>
On Tue, Jul 05, 2016 at 10:34:58PM -0400, Jessica Yu wrote:
> Hi,
>
> A few months ago, Chris Arges reported a bug involving alternatives/paravirt
> patching that was discussed here [1] and here [2]. To briefly summarize the
> bug, patch modules that contained .altinstructions or .parainstructions
> sections would break because these alternative/paravirt patches would be
> applied first by the module loader (see x86 module_finalize()), then
> livepatch would later clobber these patches when applying per-object
> relocations. This lead to crashes and unpredictable behavior.
>
> One conclusion we reached from our last discussion was that we will
> need to introduce some arch-specific code to address this problem.
> This patchset presents a possible fix for the bug by adding a new
> arch-specific arch_klp_init_object_loaded() function that by default
> does nothing but can be overridden by different arches.
>
> To fix this issue for x86, since we can access a patch module's Elf
> sections through mod->klp_info, we can simply delay the calls to
> apply_paravirt() and apply_alternatives() to arch_klp_init_object_loaded(),
> which is called after relocations have been written for an object.
> In addition, for patch modules, .parainstructions and .altinstructions are
> prefixed by ".klp.arch.${objname}" so that the module loader ignores them
> and livepatch can apply them manually.
>
> Currently for kpatch, we don't support including jump table sections in
> the patch module, and supporting .smp_locks is currently broken, so we
> don't consider those sections (for now).
>
> I did some light testing with some patches to kvm and verified that the
> original issue reported in [2] was fixed.
>
> Based on linux-next.
>
Jessica,
I was able to test these patches on top of linux-next. I took your kpatch
branch and hacked it a bit to get it working and was able to
apply a patch to 'kvm_arch_vm_ioctl' while running a VM workload.
Great job!
Tested-by: Chris J Arges <chris.j.arges@canonical.com>
--chris
> [1] http://thread.gmane.org/gmane.linux.kernel/2185604/
> [2] https://github.com/dynup/kpatch/issues/580
>
> Jessica Yu (2):
> livepatch: use arch_klp_init_object_loaded() to finish arch-specific tasks
> livepatch/x86: apply alternatives and paravirt patches after relocations
>
> arch/x86/kernel/Makefile | 1 +
> arch/x86/kernel/livepatch.c | 66 +++++++++++++++++++++++++++++++++++++++++++++
> include/linux/livepatch.h | 3 +++
> kernel/livepatch/core.c | 12 +++++++--
> 4 files changed, 80 insertions(+), 2 deletions(-)
> create mode 100644 arch/x86/kernel/livepatch.c
>
> --
> 2.4.3
>
next prev parent reply other threads:[~2016-07-08 5:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-06 2:34 [PATCH 0/2] Fix issue with alternatives/paravirt patches Jessica Yu
2016-07-06 2:34 ` [PATCH 1/2] livepatch: use arch_klp_init_object_loaded() to finish arch-specific tasks Jessica Yu
2016-07-06 2:35 ` [PATCH 2/2] livepatch/x86: apply alternatives and paravirt patches after relocations Jessica Yu
2016-07-08 15:44 ` Josh Poimboeuf
2016-07-07 15:56 ` [PATCH 0/2] Fix issue with alternatives/paravirt patches Petr Mladek
2016-07-07 22:53 ` Josh Poimboeuf
2016-07-12 11:55 ` Miroslav Benes
2016-07-12 14:01 ` Josh Poimboeuf
2016-07-13 1:18 ` Jessica Yu
2016-07-07 23:51 ` Jessica Yu
2016-07-08 5:22 ` Christopher Arges [this message]
2016-07-08 16:57 ` Jessica Yu
2016-07-12 12:06 ` [PATCH 0/2] " Miroslav Benes
2016-07-21 5:10 ` Jessica Yu
2016-07-21 8:48 ` Miroslav Benes
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=20160708052222.GA1549@gmail.com \
--to=chris.j.arges@canonical.com \
--cc=eugene.shatokhin@rosalab.ru \
--cc=jeyu@redhat.com \
--cc=jikos@kernel.org \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=pmladek@suse.com \
--cc=x86@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 NNTP newsgroup(s).