From: Jiri Kosina <jikos@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Josh Poimboeuf <jpoimboe@redhat.com>,
Miroslav Benes <mbenes@suse.cz>, Petr Mladek <pmladek@suse.com>,
Joe Lawrence <joe.lawrence@redhat.com>,
linux-kernel@vger.kernel.org, live-patching@vger.kernel.org
Subject: [GIT PULL] livepatching for 5.8
Date: Wed, 3 Jun 2020 22:42:14 +0200 (CEST) [thread overview]
Message-ID: <nycvar.YFH.7.76.2006032232540.13242@cbobk.fhfr.pm> (raw)
Linus,
please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/livepatching/livepatching.git for-linus
to receive livepatching subsystem updates for 5.8.
You are going to get a minor conflict with modules tree; the correct
resolution is documented at
http://lore.kernel.org/r/20200508180524.6995b07e@canb.auug.org.au
Alternatively, I can just prepare a branch for you to pull with the
conflict resolved.
Thanks.
=====
- simplifications and improvements for issues Peter Ziljstra found during
his previous work on W^X cleanups. This allows us to remove livepatch
arch-specific .klp.arch sections and add proper support for jump labels
in patched code. Also, this patchset removes the last
module_disable_ro() usage in the tree. Patches from Josh Poimboeuf and
Peter Zijlstra
- a few other minor cleanups
=====
----------------------------------------------------------------
Jiri Kosina (1):
livepatch: add arch-specific headers to MAINTAINERS
Josh Poimboeuf (8):
livepatch: Disallow vmlinux.ko
livepatch: Apply vmlinux-specific KLP relocations early
livepatch: Prevent module-specific KLP rela sections from referencing vmlinux symbols
s390: Change s390_kernel_write() return type to match memcpy()
livepatch: Remove module_disable_ro() usage
module: Remove module_disable_ro()
x86/module: Use text_mutex in apply_relocate_add()
module: Make module_enable_ro() static again
Kamalesh Babulal (1):
MAINTAINERS: add lib/livepatch to LIVE PATCHING
Lukas Bulwahn (1):
MAINTAINERS: adjust to livepatch .klp.arch removal
Peter Zijlstra (3):
livepatch: Remove .klp.arch
s390/module: Use s390_kernel_write() for late relocations
x86/module: Use text_poke() for late relocations
Samuel Zou (1):
livepatch: Make klp_apply_object_relocs static
Documentation/livepatch/module-elf-format.rst | 15 +--
MAINTAINERS | 4 +-
arch/s390/include/asm/uaccess.h | 2 +-
arch/s390/kernel/module.c | 147 ++++++++++++---------
arch/s390/mm/maccess.c | 9 +-
arch/um/kernel/um_arch.c | 16 +++
arch/x86/kernel/Makefile | 1 -
arch/x86/kernel/livepatch.c | 53 --------
arch/x86/kernel/module.c | 43 ++++++-
include/linux/livepatch.h | 17 ++-
include/linux/module.h | 8 --
kernel/livepatch/core.c | 178 ++++++++++++++++----------
kernel/module.c | 26 ++--
13 files changed, 283 insertions(+), 236 deletions(-)
delete mode 100644 arch/x86/kernel/livepatch.c
--
Jiri Kosina
SUSE Labs
next reply other threads:[~2020-06-03 20:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-03 20:42 Jiri Kosina [this message]
2020-06-04 18:25 ` [GIT PULL] livepatching for 5.8 pr-tracker-bot
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=nycvar.YFH.7.76.2006032232540.13242@cbobk.fhfr.pm \
--to=jikos@kernel.org \
--cc=joe.lawrence@redhat.com \
--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=torvalds@linux-foundation.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).