From: Rusty Russell <rusty@rustcorp.com.au>
To: <torvalds@linux-foundation.org>
Cc: "lkml" <linux-kernel@vger.kernel.org>
Cc: Ben Hutchings <ben@decadent.org.uk>
Cc: Jessica Yu <jeyu@redhat.com>
Cc: Jiri Kosina <jkosina@suse.cz>
Cc: Kees Cook <keescook@chromium.org>
Cc: Libor Pechacek <lpechacek@suse.com>
Cc: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: Prarit Bhargava <prarit@redhat.com>
Cc: Steven Rostedt <rostedt@goodmis.org>
Subject: [PULL] modules-next
Date: Mon, 01 Aug 2016 10:32:21 +0930 [thread overview]
Message-ID: <87y44hxpwi.fsf@rustcorp.com.au> (raw)
The following changes since commit 3fc9d690936fb2e20e180710965ba2cc3a0881f8:
Merge branch 'for-4.8/drivers' of git://git.kernel.dk/linux-block (2016-07-26 15:37:51 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/rusty/linux.git tags/modules-next-for-linus
for you to fetch changes up to 8acc0026b0f3046c9929d1f33cf840cd190d1b12:
extable.h: add stddef.h so "NULL" definition is not implicit (2016-07-28 15:23:47 +0930)
----------------------------------------------------------------
Only interesting thing here is Jessica's patch to add ro_after_init support
to modules. The rest are all trivia.
Cheers,
Rusty.
----------------------------------------------------------------
Ben Hutchings (3):
module: Invalidate signatures on force-loaded modules
Documentation/module-signing.txt: Note need for version info if reusing a key
module: Disable MODULE_FORCE_LOAD when MODULE_SIG_FORCE is enabled
Jessica Yu (1):
modules: add ro_after_init support
Jiri Kosina (1):
module: fix noreturn attribute for __module_put_and_exit()
Libor Pechacek (1):
module: Issue warnings when tainting kernel
Paul Gortmaker (2):
exceptions: fork exception table content from module.h into extable.h
extable.h: add stddef.h so "NULL" definition is not implicit
Prarit Bhargava (1):
modules: Add kernel parameter to blacklist modules
Rusty Russell (2):
module: fix redundant test.
jump_label: disable preemption around __module_text_address().
Steven Rostedt (1):
module: Do a WARN_ON_ONCE() for assert module mutex not held
Documentation/kernel-parameters.txt | 3 +
Documentation/module-signing.txt | 6 ++
include/linux/extable.h | 32 ++++++++++
include/linux/module.h | 37 +++--------
include/uapi/linux/elf.h | 1 +
init/Kconfig | 1 +
kernel/jump_label.c | 5 +-
kernel/livepatch/core.c | 2 +-
kernel/module.c | 121 +++++++++++++++++++++++++++++-------
9 files changed, 156 insertions(+), 52 deletions(-)
create mode 100644 include/linux/extable.h
next reply other threads:[~2016-08-01 1:02 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-01 1:02 Rusty Russell [this message]
2016-08-01 1:44 ` Linus Torvalds
2016-08-01 19:11 ` Ben Hutchings
2016-08-02 0:10 ` Rusty Russell
2016-08-04 0:50 ` Rusty Russell
-- strict thread matches above, loose matches on Subject: below --
2015-11-08 23:42 Rusty Russell
2015-06-30 2:47 Rusty Russell
2015-02-13 6:43 Rusty Russell
2014-12-19 0:55 Rusty Russell
2014-12-19 5:01 ` Linus Torvalds
2014-12-22 1:21 ` Rusty Russell
2014-09-16 15:48 Rusty Russell
2014-08-11 2:32 Rusty Russell
2014-06-11 5:33 Rusty Russell
2014-06-11 10:55 ` Mark Brown
2014-06-12 1:25 ` Rusty Russell
2014-06-12 11:27 ` Mark Brown
2014-06-13 1:03 ` Rusty Russell
2014-06-13 9:24 ` Mark Brown
2014-06-13 10:04 ` Geert Uytterhoeven
2013-07-10 3:55 Rusty Russell
2013-02-19 23:14 Rusty Russell
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=87y44hxpwi.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=linux-kernel@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
Powered by JetHome