From: Andrew Morton <akpm@linux-foundation.org>
To: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: Ingo Molnar <mingo@elte.hu>, Gautham R Shenoy <ego@in.ibm.com>,
Paul Jackson <pj@sgi.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sched: missing locking in sched_domains code
Date: Mon, 28 Apr 2008 02:31:39 -0700 [thread overview]
Message-ID: <20080428023139.fe318427.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080428091745.GB27056@osiris.boeblingen.de.ibm.com>
On Mon, 28 Apr 2008 11:17:45 +0200 Heiko Carstens <heiko.carstens@de.ibm.com> wrote:
> On Mon, Apr 28, 2008 at 01:57:23AM -0700, Andrew Morton wrote:
> > On Mon, 28 Apr 2008 10:49:04 +0200 Heiko Carstens <heiko.carstens@de.ibm.com> wrote:
> > > /* doms_cur_mutex serializes access to doms_cur[] array */
> > > -static DEFINE_MUTEX(doms_cur_mutex);
> > > +static DEFINE_MUTEX(sched_domains_mutex);
> >
> > The comment refers to a no-longer-existing lock, and no longer correctly
> > describes the lock's usage.
>
> version 42. Please feel free to change the comment if you think it could
> be better :)
Actually, it's a pretty bad comment ;)
> +/* sched_domains_mutex serializes calls to arch_init_sched_domains,
> + * detach_destroy_domains and partition_sched_domains.
> + */
locks protect *data*, not "calls". This matters. Which data is actually
protected by this lock??
next prev parent reply other threads:[~2008-04-28 9:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-27 21:12 [PATCH] sched: missing locking in sched_domains code Heiko Carstens
2008-04-28 1:39 ` Andrew Morton
2008-04-28 7:09 ` Heiko Carstens
2008-04-28 7:24 ` Ingo Molnar
2008-04-28 7:28 ` Andrew Morton
2008-04-28 7:52 ` Heiko Carstens
2008-04-28 8:11 ` Heiko Carstens
2008-04-28 8:32 ` Ingo Molnar
2008-04-28 8:49 ` Heiko Carstens
2008-04-28 8:57 ` Andrew Morton
2008-04-28 9:17 ` Heiko Carstens
2008-04-28 9:31 ` Andrew Morton [this message]
2008-04-28 9:33 ` Heiko Carstens
2008-04-28 12:27 ` Ingo Molnar
2008-04-28 13:13 ` Ingo Molnar
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=20080428023139.fe318427.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ego@in.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=pj@sgi.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.