All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: "Linus Torvalds" <torvalds@linux-foundation.org>
Cc: "LKML" <linux-kernel@vger.kernel.org>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Hannes Reinecke <hare@suse.de>
Cc: "Luis R. Rodriguez" <mcgrof@suse.com>
Cc: Weilong Chen <chenweilong@huawei.com>
Subject: [PULL] module fixes (stable)
Date: Wed, 10 Feb 2016 10:56:27 +1030	[thread overview]
Message-ID: <87fux1z9zg.fsf@rustcorp.com.au> (raw)

The following changes since commit 34229b277480f46c1e9a19f027f30b074512e68b:

  Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net (2016-02-01 15:56:08 -0800)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/rusty/linux.git tags/fixes-for-linus

for you to fetch changes up to 8244062ef1e54502ef55f54cced659913f244c3e:

  modules: fix longstanding /proc/kallsyms vs module insertion race. (2016-02-03 16:58:15 +1030)

----------------------------------------------------------------
Fix for async_probe module param added in 4.3 (clearly not widely used yet),
and a much more interesting kallsyms race which has been around approximately
forever.  This fix is more invasive, and will require some care in backporting,
but I hated all the bandaids I could think of, so...

There are some more coming, which are only for breakages introduced this
cycle (livepatch), but wanted these in now.

Thanks,
Rusty.

----------------------------------------------------------------
Luis R. Rodriguez (1):
      modules: fix modparam async_probe request

Rusty Russell (2):
      module: wrapper for symbol name.
      modules: fix longstanding /proc/kallsyms vs module insertion race.

 include/linux/module.h |  19 ++++----
 kernel/module.c        | 120 ++++++++++++++++++++++++++++++-------------------
 2 files changed, 85 insertions(+), 54 deletions(-)

                 reply	other threads:[~2016-02-10  0:29 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=87fux1z9zg.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.