From: Rusty Russell <rusty@rustcorp.com.au>
To: linux-kernel@vger.kernel.org
Cc: Rusty Russell <rusty@rustcorp.com.au>,
Weilong Chen <chenweilong@huawei.com>,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
Peter Zijlstra <peterz@infradead.org>
Subject: [PATCH 0/3] module stable fixes.
Date: Fri, 5 Feb 2016 10:44:10 +1030 [thread overview]
Message-ID: <1454631253-14379-1-git-send-email-rusty@rustcorp.com.au> (raw)
Luis' async_probe is a recent issue, but the /proc/kallsyms vs
module insertion race has been the for a long time, maybe forever.
I expect some pain in backporting that fix, but mainly textual,
and there's no simpler fix (grabbing the mutex for /proc/kallsyms
would solve the reported case, but not fix it for the other kallsyms
users).
If no complaints, I'll send Linus a pull req.
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(-)
--
2.5.0
next reply other threads:[~2016-02-05 0:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-05 0:14 Rusty Russell [this message]
2016-02-05 0:14 ` [PATCH 1/3] modules: fix modparam async_probe request Rusty Russell
2016-02-05 0:14 ` [PATCH 2/3] module: wrapper for symbol name Rusty Russell
2016-02-05 6:45 ` 平松雅巳 / HIRAMATU，MASAMI
2016-02-05 0:14 ` [PATCH 3/3] modules: fix longstanding /proc/kallsyms vs module insertion race Rusty Russell
2016-02-05 6:41 ` 平松雅巳 / HIRAMATU，MASAMI
2016-02-05 6:51 ` [PATCH 0/3] module stable fixes 平松雅巳 / HIRAMATU，MASAMI
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=1454631253-14379-1-git-send-email-rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=chenweilong@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=peterz@infradead.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).