From: Cong Wang <xiyou.wangcong@gmail.com>
To: "Chen, Dennis (SRDC SW)" <Dennis1.Chen@amd.com>
Cc: "jbaron@redhat.com" <jbaron@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] Refine mutex and rcu method in module.c, kernel<3.2.9>
Date: Sat, 10 Mar 2012 11:44:42 +0800 [thread overview]
Message-ID: <4F5ACE2A.2030807@gmail.com> (raw)
In-Reply-To: <491D6B4EAD0A714894D8AD22F4BDE043032910@SCYBEXDAG04.amd.com>
On 03/08/2012 12:48 AM, Chen, Dennis (SRDC SW) wrote:
> Adding dynamic debug maintainer -- Jason Baron...
>
> -----Original Message-----
> From: Chen, Dennis (SRDC SW)
> Sent: Wednesday, March 07, 2012 10:57 PM
> To: linux-kernel@vger.kernel.org
> Cc: Chen, Dennis (SRDC SW)
> Subject: [PATCH 2/2] Refine mutex and rcu method in module.c, kernel<3.2.9>
>
> 1. Add protection code for module_bug_list readers
> 2. Add a new module_bug_mutex as the mutex of the module_bug_list writers
Take a look at the comments in the code:
/*
* Strictly speaking this should have a spinlock to protect against
* traversals, but since we only traverse on BUG()s, a spinlock
* could potentially lead to deadlock and thus be
counter-productive.
*/
module_find_bug() is called in a dying path...
next prev parent reply other threads:[~2012-03-10 3:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-07 14:51 [PATCH 1/2] Refine mutex and rcu method in module.c, kernel<3.2.9> Chen, Dennis (SRDC SW)
2012-03-07 14:57 ` [PATCH 2/2] " Chen, Dennis (SRDC SW)
2012-03-07 16:48 ` Chen, Dennis (SRDC SW)
2012-03-10 3:44 ` Cong Wang [this message]
2012-03-07 15:37 ` [PATCH 1/2] " Cong Wang
2012-03-07 15:52 ` Chen, Dennis (SRDC SW)
2012-03-10 3:42 ` Cong Wang
2012-03-07 16:46 ` Chen, Dennis (SRDC SW)
2012-03-08 9:18 ` Rusty Russell
2012-03-08 12:18 ` Chen, Dennis (SRDC SW)
2012-03-08 16:13 ` Chen, Dennis (SRDC SW)
2012-03-10 4:26 ` Cong Wang
2012-03-11 14:56 ` Paul E. McKenney
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=4F5ACE2A.2030807@gmail.com \
--to=xiyou.wangcong@gmail.com \
--cc=Dennis1.Chen@amd.com \
--cc=jbaron@redhat.com \
--cc=linux-kernel@vger.kernel.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.