From: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
To: Andi Kleen <andi@firstfloor.org>
Cc: jbaron@redhat.com, rostedt@goodmis.org,
linux-kernel@vger.kernel.org, mingo@elte.hu, hpa@zytor.com,
tglx@linutronix.de, roland@redhat.com, rth@redhat.com,
mhiramat@redhat.com, fweisbec@gmail.com, avi@redhat.com,
davem@davemloft.net, vgoyal@redhat.com, sam@ravnborg.org,
tony@bakeyournoodle.com, Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH 1/2] Add for_each_module iterator function v2
Date: Wed, 22 Sep 2010 10:14:32 -0400 [thread overview]
Message-ID: <20100922141432.GB30730@Krystal> (raw)
In-Reply-To: <1285162001-9556-1-git-send-email-andi@firstfloor.org>
* Andi Kleen (andi@firstfloor.org) wrote:
> From: Andi Kleen <ak@linux.intel.com>
>
> This is a generic function to iterate over all modules.
> To be used in the next patch.
>
> v2: Use module_mutex instead of preempt disabling
>
> Signed-off-by: Andi Kleen <ak@linux.intel.com>
> ---
> include/linux/module.h | 1 +
> kernel/module.c | 10 ++++++++++
> 2 files changed, 11 insertions(+), 0 deletions(-)
>
> diff --git a/include/linux/module.h b/include/linux/module.h
> index 403ac26..809b6db 100644
> --- a/include/linux/module.h
> +++ b/include/linux/module.h
> @@ -410,6 +410,7 @@ struct module *__module_address(unsigned long addr);
> bool is_module_address(unsigned long addr);
> bool is_module_percpu_address(unsigned long addr);
> bool is_module_text_address(unsigned long addr);
> +void for_each_module(void (*op)(struct module *, void *arg), void *arg);
>
> static inline int within_module_core(unsigned long addr, struct module *mod)
> {
> diff --git a/kernel/module.c b/kernel/module.c
> index eba1341..9e2a561 100644
> --- a/kernel/module.c
> +++ b/kernel/module.c
> @@ -384,6 +384,16 @@ struct module *find_module(const char *name)
> }
> EXPORT_SYMBOL_GPL(find_module);
>
> +void for_each_module(void (*op)(struct module *, void *arg), void *arg)
> +{
> + struct module *mod;
> +
> + mutex_lock(&module_mutex);
I'm concerned about the following mutex dependency chain:
module_mutex -> jump_label_mutex (on module load)
jump_label_mutex -> module_mutex (on jump_label_update)
Actually, I think your module notifier is missing in your version. This
is why you don't see this dependency problem.
Mathieu
> + list_for_each_entry_rcu(mod, &modules, list)
> + op(mod, arg);
> + mutex_unlock(&module_mutex);
> +}
> +
> #ifdef CONFIG_SMP
>
> static inline void __percpu *mod_percpu(struct module *mod)
> --
> 1.7.1
>
--
Mathieu Desnoyers
Operating System Efficiency R&D Consultant
EfficiOS Inc.
http://www.efficios.com
next prev parent reply other threads:[~2010-09-22 14:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-22 13:26 [PATCH 1/2] Add for_each_module iterator function v2 Andi Kleen
2010-09-22 13:26 ` [PATCH 2/2] Rewrite jump_label.c to use binary search v2 Andi Kleen
2010-09-22 14:14 ` Mathieu Desnoyers [this message]
2010-09-22 14:29 ` [PATCH 1/2] Add for_each_module iterator function v2 Jason Baron
2010-09-22 14:35 ` Andi Kleen
2010-09-22 14:50 ` Frederic Weisbecker
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=20100922141432.GB30730@Krystal \
--to=mathieu.desnoyers@polymtl.ca \
--cc=ak@linux.intel.com \
--cc=andi@firstfloor.org \
--cc=avi@redhat.com \
--cc=davem@davemloft.net \
--cc=fweisbec@gmail.com \
--cc=hpa@zytor.com \
--cc=jbaron@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@redhat.com \
--cc=mingo@elte.hu \
--cc=roland@redhat.com \
--cc=rostedt@goodmis.org \
--cc=rth@redhat.com \
--cc=sam@ravnborg.org \
--cc=tglx@linutronix.de \
--cc=tony@bakeyournoodle.com \
--cc=vgoyal@redhat.com \
/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.