From: Rusty Russell <rusty@rustcorp.com.au>
To: Peter Zijlstra <peterz@infradead.org>,
mingo@kernel.org, mathieu.desnoyers@efficios.com,
oleg@redhat.com, paulmck@linux.vnet.ibm.com,
torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, andi@firstfloor.org,
rostedt@goodmis.org, tglx@linutronix.de, peterz@infradead.org,
Jason Baron <jbaron@akamai.com>
Subject: Re: [PATCH 3/8] module, jump_label: Fix module locking
Date: Fri, 20 Mar 2015 14:56:25 +1030 [thread overview]
Message-ID: <87egokjnv2.fsf@rustcorp.com.au> (raw)
In-Reply-To: <20150318134631.743042205@infradead.org>
Peter Zijlstra <peterz@infradead.org> writes:
> As per the module core lockdep annotations:
>
> [ 18.034047] ---[ end trace 9294429076a9c673 ]---
> [ 18.047760] Hardware name: Intel Corporation S2600GZ/S2600GZ, BIOS SE5C600.86B.02.02.0002.122320131210 12/23/2013
> [ 18.059228] ffffffff817d8676 ffff880036683c38 ffffffff8157e98b 0000000000000001
> [ 18.067541] 0000000000000000 ffff880036683c78 ffffffff8105fbc7 ffff880036683c68
> [ 18.075851] ffffffffa0046b08 0000000000000000 ffffffffa0046d00 ffffffffa0046cc8
> [ 18.084173] Call Trace:
> [ 18.086906] [<ffffffff8157e98b>] dump_stack+0x4f/0x7b
> [ 18.092649] [<ffffffff8105fbc7>] warn_slowpath_common+0x97/0xe0
> [ 18.099361] [<ffffffff8105fc2a>] warn_slowpath_null+0x1a/0x20
> [ 18.105880] [<ffffffff810ee502>] __module_address+0x1d2/0x1e0
> [ 18.112400] [<ffffffff81161153>] jump_label_module_notify+0x143/0x1e0
> [ 18.119710] [<ffffffff810814bf>] notifier_call_chain+0x4f/0x70
> [ 18.126326] [<ffffffff8108160e>] __blocking_notifier_call_chain+0x5e/0x90
> [ 18.134009] [<ffffffff81081656>] blocking_notifier_call_chain+0x16/0x20
> [ 18.141490] [<ffffffff810f0f00>] load_module+0x1b50/0x2660
> [ 18.147720] [<ffffffff810f1ade>] SyS_init_module+0xce/0x100
> [ 18.154045] [<ffffffff81587429>] system_call_fastpath+0x12/0x17
> [ 18.160748] ---[ end trace 9294429076a9c674 ]---
>
> Jump labels is not doing it right; fix this.
>
> Cc: Rusty Russell <rusty@rustcorp.com.au>
> Cc: Jason Baron <jbaron@akamai.com>
> Acked-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
> ---
> kernel/jump_label.c | 21 +++++++++++++++++----
> 1 file changed, 17 insertions(+), 4 deletions(-)
>
> --- a/kernel/jump_label.c
> +++ b/kernel/jump_label.c
> @@ -280,6 +280,17 @@ void jump_label_apply_nops(struct module
> }
> }
>
> +static inline bool address_in_module(unsigned long addr, struct module *mod)
> +{
> + bool ret;
> +
> + preempt_disable();
> + ret = __module_address(addr) == mod;
> + preempt_enable();
> +
> + return ret;
> +}
> +
> static int jump_label_add_module(struct module *mod)
> {
> struct jump_entry *iter_start = mod->jump_entries;
> @@ -302,7 +313,7 @@ static int jump_label_add_module(struct
> continue;
>
> key = iterk;
> - if (__module_address(iter->key) == mod) {
> + if (address_in_module(iter->key, mod)) {
> /*
> * Set key->entries to iter, but preserve JUMP_LABEL_TRUE_BRANCH.
> */
> @@ -339,7 +350,7 @@ static void jump_label_del_module(struct
>
> key = (struct static_key *)(unsigned long)iter->key;
>
> - if (__module_address(iter->key) == mod)
> + if (address_in_module(iter->key, mod))
> continue;
>
> prev = &key->next;
Using __module_address() for this was just plain weird in the first
place. How about:
if (within_module(iter->key, mod))
Cheers,
Rusty.
next prev parent reply other threads:[~2015-03-20 4:27 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-18 13:36 [PATCH 0/8] latched RB-trees and __module_address() Peter Zijlstra
2015-03-18 13:36 ` [PATCH 1/8] module: Sanitize RCU usage and locking Peter Zijlstra
2015-03-20 3:36 ` Rusty Russell
2015-03-18 13:36 ` [PATCH 2/8] module: Annotate module version magic Peter Zijlstra
2015-03-18 13:36 ` [PATCH 3/8] module, jump_label: Fix module locking Peter Zijlstra
2015-03-20 4:26 ` Rusty Russell [this message]
2015-03-20 9:11 ` Peter Zijlstra
2015-03-18 13:36 ` [PATCH 4/8] rbtree: Make lockless searches non-fatal Peter Zijlstra
2015-03-18 13:36 ` [PATCH 5/8] seqlock: Better document raw_write_seqcount_latch() Peter Zijlstra
2015-03-18 14:29 ` Mathieu Desnoyers
2015-03-18 14:50 ` Peter Zijlstra
2015-03-18 13:36 ` [PATCH 6/8] rbtree: Implement generic latch_tree Peter Zijlstra
2015-03-18 16:20 ` Ingo Molnar
2015-03-19 5:14 ` Andrew Morton
2015-03-19 7:25 ` Peter Zijlstra
2015-03-19 20:58 ` Andrew Morton
2015-03-19 21:36 ` Steven Rostedt
2015-03-19 21:38 ` Steven Rostedt
2015-03-19 21:47 ` Andrew Morton
2015-03-19 21:54 ` Steven Rostedt
2015-03-19 22:12 ` Peter Zijlstra
2015-03-19 22:04 ` Peter Zijlstra
2015-03-20 9:50 ` Peter Zijlstra
2015-03-19 22:10 ` Peter Zijlstra
2015-03-18 13:36 ` [PATCH 7/8] module: Optimize __module_address() using a latched RB-tree Peter Zijlstra
2015-03-18 13:36 ` [PATCH 8/8] module: Use __module_address() for module_address_lookup() Peter Zijlstra
2015-03-18 14:21 ` [PATCH 0/8] latched RB-trees and __module_address() Christoph Hellwig
2015-03-18 14:38 ` Peter Zijlstra
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=87egokjnv2.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=andi@firstfloor.org \
--cc=jbaron@akamai.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--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;
as well as URLs for NNTP newsgroup(s).