From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Jessica Yu <jeyu@kernel.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Petr Mladek <pmladek@suse.com>, Jiri Kosina <jikos@kernel.org>,
Miroslav Benes <mbenes@suse.cz>,
Joe Lawrence <joe.lawrence@redhat.com>,
linux-kernel@vger.kernel.org, live-patching@vger.kernel.org,
Johannes Erdfelt <johannes@erdfelt.com>,
Ingo Molnar <mingo@kernel.org>
Subject: [PATCH 0/3] module: Livepatch/ftrace fixes
Date: Thu, 13 Jun 2019 20:07:21 -0500 [thread overview]
Message-ID: <cover.1560474114.git.jpoimboe@redhat.com> (raw)
Patch 1 fixes a module loading race between livepatch and ftrace.
Patch 2 adds lockdep assertions assocated with patch 1.
Patch 3 fixes a theoretical bug in the module __ro_after_init section
handling.
Josh Poimboeuf (3):
module: Fix livepatch/ftrace module text permissions race
module: Add text_mutex lockdep assertions for page attribute changes
module: Improve module __ro_after_init handling
arch/arm64/kernel/ftrace.c | 2 +-
include/linux/module.h | 4 ++--
kernel/livepatch/core.c | 10 ++++++++--
kernel/module.c | 29 ++++++++++++++++++++++-------
kernel/trace/ftrace.c | 10 +++++++++-
5 files changed, 42 insertions(+), 13 deletions(-)
--
2.20.1
next reply other threads:[~2019-06-14 1:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-14 1:07 Josh Poimboeuf [this message]
2019-06-14 1:07 ` [PATCH 1/3] module: Fix livepatch/ftrace module text permissions race Josh Poimboeuf
2019-06-14 21:04 ` Steven Rostedt
2019-06-26 8:22 ` Miroslav Benes
2019-06-26 13:37 ` Petr Mladek
2019-06-26 14:44 ` Thomas Gleixner
2019-06-26 14:52 ` Josh Poimboeuf
2019-06-26 14:59 ` Steven Rostedt
2019-06-14 1:07 ` [PATCH 2/3] module: Add text_mutex lockdep assertions for page attribute changes Josh Poimboeuf
2019-06-14 14:04 ` Petr Mladek
2019-06-14 18:21 ` Josh Poimboeuf
2019-06-14 1:07 ` [PATCH 3/3] module: Improve module __ro_after_init handling Josh Poimboeuf
2019-06-14 14:14 ` Petr Mladek
2019-06-14 18:23 ` Josh Poimboeuf
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=cover.1560474114.git.jpoimboe@redhat.com \
--to=jpoimboe@redhat.com \
--cc=jeyu@kernel.org \
--cc=jikos@kernel.org \
--cc=joe.lawrence@redhat.com \
--cc=johannes@erdfelt.com \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=mingo@kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.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
Powered by JetHome