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 5.17
Date: Fri, 14 Jan 2022 16:57:27 +0100 [thread overview]
Message-ID: <20220114155727.GA17419@pathway.suse.cz> (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-5.17
====================================
+ Correctly handle kobjects when a livepatch init fails.
+ Avoid CPU hogging when searching for many livepatched symbols.
+ Add livepatch API page into documentation.
----------------------------------------------------------------
David Vernet (3):
Documentation: livepatch: Add livepatch API page
livepatch: Fix kobject refcount bug on klp_init_patch_early failure path
livepatch: Avoid CPU hogging with cond_resched
Petr Mladek (1):
Merge branch 'for-5.17/kallsyms' into for-linus
Yang Yingliang (1):
livepatch: Fix missing unlock on error in klp_enable_patch()
Documentation/livepatch/api.rst | 30 ++++++++++++++++++++++++++++++
Documentation/livepatch/index.rst | 1 +
Documentation/livepatch/shadow-vars.rst | 4 ++--
Documentation/livepatch/system-state.rst | 4 ++--
kernel/kallsyms.c | 1 +
kernel/livepatch/core.c | 29 +++++++++++++----------------
kernel/livepatch/shadow.c | 6 +++---
kernel/module.c | 2 ++
8 files changed, 54 insertions(+), 23 deletions(-)
create mode 100644 Documentation/livepatch/api.rst
next reply other threads:[~2022-01-14 15:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-14 15:57 Petr Mladek [this message]
2022-01-16 8:22 ` [GIT PULL] livepatching for 5.17 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=20220114155727.GA17419@pathway.suse.cz \
--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