From: Jason Wessel <jason.wessel@windriver.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: linux-kernel@vger.kernel.org, rusty@rustcorp.com.au,
kgdb-bugreport@lists.sourceforge.net
Subject: Re: [PATCH 16/21] KGDB: This allows for KGDB to better deal with autoloaded modules.
Date: Thu, 17 Jan 2008 08:18:09 -0600 [thread overview]
Message-ID: <478F63A1.3030509@windriver.com> (raw)
In-Reply-To: <478F5E82.8060300@siemens.com>
Jan Kiszka wrote:
> These days, notify_mutex should better be a real mutex.
>
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
>
> ---
> kernel/module.c | 14 +++++++-------
> 1 file changed, 7 insertions(+), 7 deletions(-)
>
> Index: b/kernel/module.c
> ===================================================================
> --- a/kernel/module.c
> +++ b/kernel/module.c
> @@ -66,7 +66,7 @@ extern int module_sysfs_initialized;
> * (add/delete uses stop_machine). */
> static DEFINE_MUTEX(module_mutex);
> static LIST_HEAD(modules);
> -static DECLARE_MUTEX(notify_mutex);
> +static DEFINE_MUTEX(notify_mutex);
>
> static BLOCKING_NOTIFIER_HEAD(module_notify_list);
>
> @@ -712,10 +712,10 @@ sys_delete_module(const char __user *nam
> if (ret != 0)
> goto out;
>
> - down(¬ify_mutex);
> + mutex_lock(¬ify_mutex);
> blocking_notifier_call_chain(&module_notify_list, MODULE_STATE_GOING,
> mod);
> - up(¬ify_mutex);
> + mutex_unlock(¬ify_mutex);
>
>
> /* Never wait if forced. */
> @@ -730,10 +730,10 @@ sys_delete_module(const char __user *nam
> }
> free_module(mod);
>
> - down(¬ify_mutex);
> + mutex_lock(¬ify_mutex);
> blocking_notifier_call_chain(&module_notify_list, MODULE_STATE_GONE,
> NULL);
> - up(¬ify_mutex);
> + mutex_unlock(¬ify_mutex);
>
> out:
> mutex_unlock(&module_mutex);
> @@ -2182,11 +2182,11 @@ sys_init_module(void __user *umod,
> /* Init routine failed: abort. Try to protect us from
> buggy refcounters. */
> mod->state = MODULE_STATE_GOING;
> - down(¬ify_mutex);
> + mutex_lock(¬ify_mutex);
> blocking_notifier_call_chain(&module_notify_list,
> MODULE_STATE_GOING,
> mod);
> - up(¬ify_mutex);
> + mutex_unlock(¬ify_mutex);
> synchronize_sched();
> module_put(mod);
> mutex_lock(&module_mutex);
>
Jan,
This looks fine.
I committed this to the latest development branch as well as the 2.6.24
branch. It will show up in the kernel.org & cvs repository later today.
Thanks,
Jason.
next prev parent reply other threads:[~2008-01-17 14:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-15 18:33 [PATCH 16/21] KGDB: This allows for KGDB to better deal with autoloaded modules Jason Wessel
2008-01-17 13:56 ` Jan Kiszka
2008-01-17 14:18 ` Jason Wessel [this message]
[not found] ` <200801180833.08185.rusty@rustcorp.com.au>
2008-01-25 22:11 ` Jason Wessel
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=478F63A1.3030509@windriver.com \
--to=jason.wessel@windriver.com \
--cc=jan.kiszka@siemens.com \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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.