From: Petr Mladek <pmladek@suse.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, live-patching@vger.kernel.org
Subject: [GIT PULL] livepatching for 6.1
Date: Wed, 5 Oct 2022 13:29:06 +0200 [thread overview]
Message-ID: <Yz1qgrJA+wmbVILN@alley> (raw)
Hi Linus,
please pull the latest livepatching changes from
git://git.kernel.org/pub/scm/linux/kernel/git/livepatching/livepatching.git tags/livepatching-for-6.1
==================================
- Fix race between fork and livepatch transition revert.
- Add sysfs entry that shows "patched" state for each object (module)
that can be livepatched by the given livepatch.
- Some clean up.
----------------------------------------------------------------
Joe Lawrence (1):
selftests/livepatch: normalize sysctl error message
Petr Mladek (1):
Merge branch 'for-6.1/sysfs-patched-object' into for-linus
Rik van Riel (1):
livepatch: fix race between fork and KLP transition
Song Liu (2):
livepatch: add sysfs entry "patched" for each klp_object
selftests/livepatch: add sysfs test
Zhen Lei (1):
livepatch: Add a missing newline character in klp_module_coming()
Documentation/ABI/testing/sysfs-kernel-livepatch | 8 +++
kernel/livepatch/core.c | 20 +++++-
kernel/livepatch/transition.c | 18 ++++-
tools/testing/selftests/livepatch/Makefile | 3 +-
tools/testing/selftests/livepatch/functions.sh | 36 +++++++++-
tools/testing/selftests/livepatch/test-sysfs.sh | 86 ++++++++++++++++++++++++
6 files changed, 166 insertions(+), 5 deletions(-)
create mode 100755 tools/testing/selftests/livepatch/test-sysfs.sh
next reply other threads:[~2022-10-05 11:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-05 11:29 Petr Mladek [this message]
2022-10-10 18:47 ` 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=Yz1qgrJA+wmbVILN@alley \
--to=pmladek@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--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
all inboxes | Powered by JetHome®