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.18
Date: Mon, 28 Mar 2022 13:30:17 +0200 [thread overview]
Message-ID: <YkGcSUol2xzW62tQ@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-5.18
========================================
- Forced transitions block only to-be-removed livepatches. [Chengming]
- Detect when ftrace handler could not be disabled in self-tests. [David]
- Calm down warning from a static analyzer. [Tom]
----------------------------------------------------------------
Chengming Zhou (1):
livepatch: Don't block removal of patches that are safe to unload
David Vernet (1):
livepatch: Skip livepatch tests if ftrace cannot be configured
Petr Mladek (1):
Merge branch 'for-5.18/selftests-fixes' into for-linus
Tom Rix (1):
livepatch: Reorder to use before freeing a pointer
kernel/livepatch/transition.c | 11 +++++++++--
samples/livepatch/livepatch-shadow-fix1.c | 2 +-
samples/livepatch/livepatch-shadow-fix2.c | 2 +-
tools/testing/selftests/livepatch/functions.sh | 22 +++++++++++++++++++---
tools/testing/selftests/livepatch/test-ftrace.sh | 3 ++-
5 files changed, 32 insertions(+), 8 deletions(-)
next reply other threads:[~2022-03-28 11:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-28 11:30 Petr Mladek [this message]
2022-03-28 22:06 ` [GIT PULL] livepatching for 5.18 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=YkGcSUol2xzW62tQ@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).