mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: "Linus Torvalds" <torvalds@linux-foundation.org>
Cc: Ionut Alexa <ionut.m.alexa@gmail.com>
Cc: Kees Cook <keescook@chromium.org>
Cc: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
Cc: "lkml" <linux-kernel@vger.kernel.org>
Subject: [PULL] modules-next
Date: Fri, 19 Dec 2014 11:25:18 +1030	[thread overview]
Message-ID: <8761d8tq4p.fsf@rustcorp.com.au> (raw)

The following changes since commit 0df1f2487d2f0d04703f142813d53615d62a1da4:

  Linux 3.18-rc3 (2014-11-02 15:01:51 -0800)

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 b0a65b0cccd477b2fd8b7adad0ac39433df54829:

  param: do not set store func without write perm (2014-12-18 12:38:51 +1030)

----------------------------------------------------------------
The exciting thing here is the getting rid of stop_machine on module
removal.  This is possible by using a simple atomic_t for the counter,
rather than our fancy per-cpu counter: it turns out that no one is doing
a module increment per net packet, so the slowdown should be in the noise.

Also, script fixed for new git version.

Cheers,
Rusty.

----------------------------------------------------------------
Ionut Alexa (1):
      kernel:module Fix coding style errors and warnings.

Kees Cook (1):
      param: do not set store func without write perm

Masami Hiramatsu (5):
      module: Wait for RCU synchronizing before releasing a module
      module: Unlink module with RCU synchronizing instead of stop_machine
      lib/bug: Use RCU list ops for module_bug_list
      module: Replace module_ref with atomic_t refcnt
      module: Remove stop_machine from module unloading

Rusty Russell (1):
      params: cleanup sysfs allocation

 include/linux/module.h        |  16 +---
 include/trace/events/module.h |   2 +-
 kernel/module.c               | 170 +++++++++++++++++++-----------------------
 kernel/params.c               |  97 ++++++++++++------------
 lib/bug.c                     |  20 +++--
 5 files changed, 137 insertions(+), 168 deletions(-)

             reply	other threads:[~2014-12-19  1:39 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-19  0:55 Rusty Russell [this message]
2014-12-19  5:01 ` Linus Torvalds
2014-12-22  1:21   ` Rusty Russell
  -- strict thread matches above, loose matches on Subject: below --
2016-08-01  1:02 Rusty Russell
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
2015-11-08 23:42 Rusty Russell
2015-06-30  2:47 Rusty Russell
2015-02-13  6:43 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=8761d8tq4p.fsf@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=ionut.m.alexa@gmail.com \
    --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