From: Ingo Molnar <mingo@elte.hu>
To: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Rusty Russell <rusty@rustcorp.com.au>,
Nick Piggin <npiggin@kernel.dk>,
linux-kernel <linux-kernel@vger.kernel.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Andi Kleen <ak@linux.intel.com>,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] cpumask: fix lg_lock/br_lock.
Date: Wed, 29 Feb 2012 10:17:32 +0100 [thread overview]
Message-ID: <20120229091732.GA11505@elte.hu> (raw)
In-Reply-To: <4F4DBB26.2060907@linux.vnet.ibm.com>
* Srivatsa S. Bhat <srivatsa.bhat@linux.vnet.ibm.com> wrote:
> Hi Andrew,
>
> On 02/29/2012 02:57 AM, Andrew Morton wrote:
>
> > On Tue, 28 Feb 2012 09:43:59 +0100
> > Ingo Molnar <mingo@elte.hu> wrote:
> >
> >> This patch should also probably go upstream through the
> >> locking/lockdep tree? Mind sending it us once you think it's
> >> ready?
> >
> > Oh goody, that means you own
> > http://marc.info/?l=linux-kernel&m=131419353511653&w=2.
> >
>
>
> That bug got fixed sometime around Dec 2011. See commit e30e2fdf
> (VFS: Fix race between CPU hotplug and lglocks)
The lglocks code is still CPU-hotplug racy AFAICS, despite the
->cpu_lock complication:
Consider a taken global lock on a CPU:
CPU#1
...
br_write_lock(vfsmount_lock);
this takes the lock of all online CPUs: say CPU#1 and CPU#2. Now
CPU#3 comes online and takes the read lock:
CPU#3
br_read_lock(vfsmount_lock);
This will succeed while the br_write_lock() is still active,
because CPU#1 has only taken the locks of CPU#1 and CPU#2.
Crash!
The proper fix would be for CPU-online to serialize with all
known lglocks, via the notifier callback, i.e. to do something
like this:
case CPU_UP_PREPARE:
for_each_online_cpu(cpu) {
spin_lock(&name##_cpu_lock);
spin_unlock(&name##_cpu_lock);
}
...
I.e. in essence do:
case CPU_UP_PREPARE:
name##_global_lock_online();
name##_global_unlock_online();
Another detail I noticed, this bit:
register_hotcpu_notifier(&name##_lg_cpu_notifier); \
get_online_cpus(); \
for_each_online_cpu(i) \
cpu_set(i, name##_cpus); \
put_online_cpus(); \
could be something simpler and loop-less, like:
get_online_cpus();
cpumask_copy(name##_cpus, cpu_online_mask);
register_hotcpu_notifier(&name##_lg_cpu_notifier);
put_online_cpus();
Thanks,
Ingo
next prev parent reply other threads:[~2012-02-29 9:17 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-27 23:22 [PATCH] cpumask: fix lg_lock/br_lock Rusty Russell
2012-02-27 23:53 ` Andrew Morton
2012-02-28 8:43 ` Ingo Molnar
2012-02-28 11:25 ` Andi Kleen
2012-02-28 12:51 ` Ingo Molnar
2012-02-28 21:27 ` Andrew Morton
2012-02-29 5:44 ` Srivatsa S. Bhat
2012-02-29 9:17 ` Ingo Molnar [this message]
2012-02-29 11:12 ` Srivatsa S. Bhat
2012-03-01 7:38 ` Ingo Molnar
2012-03-01 9:15 ` Srivatsa S. Bhat
2012-03-01 9:45 ` Ingo Molnar
2012-03-01 9:56 ` Srivatsa S. Bhat
2012-03-01 8:12 ` Srivatsa S. Bhat
2012-03-01 8:15 ` [PATCH 1/3] CPU hotplug: Fix issues with callback registration Srivatsa S. Bhat
2012-03-01 8:16 ` [PATCH 2/3] CPU hotplug, arch/powerpc: Fix CPU hotplug " Srivatsa S. Bhat
2012-03-01 8:18 ` [PATCH 3/3] CPU hotplug, arch/sparc: " Srivatsa S. Bhat
2012-02-29 8:29 ` [PATCH] cpumask: fix lg_lock/br_lock Ingo Molnar
2012-02-29 8:58 ` Peter Zijlstra
2012-02-29 9:32 ` Ingo Molnar
2012-02-28 11:24 ` Andi Kleen
2012-03-05 7:02 ` Rusty Russell
2012-03-05 7:03 ` [PATCH 1/3] lglock: remove online variants of lock Rusty Russell
2012-04-20 11:12 ` Nick Piggin
2012-03-05 7:04 ` [PATCH 2/3] brlocks/lglocks: API cleanups Rusty Russell
2012-03-05 7:05 ` [PATCH 3/3] brlocks/lglocks: turn into functions Rusty Russell
2012-04-20 11:21 ` Nick Piggin
2012-05-07 3:39 ` Rusty Russell
2012-05-07 5:46 ` Al Viro
2012-05-08 3:59 ` [PATCH 1/3] lglock: remove online variants of lock Rusty Russell
2012-05-08 4:50 ` Al Viro
2012-05-08 6:12 ` Rusty Russell
2012-05-08 4:02 ` [PATCH 2/3] brlocks/lglocks: API cleanups Rusty Russell
2012-05-08 4:02 ` [PATCH 3/3] brlocks/lglocks: turn into functions Rusty Russell
2012-05-09 7:35 ` Nick Piggin
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=20120229091732.GA11505@elte.hu \
--to=mingo@elte.hu \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@kernel.dk \
--cc=rusty@rustcorp.com.au \
--cc=srivatsa.bhat@linux.vnet.ibm.com \
--cc=viro@zeniv.linux.org.uk \
/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).