[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4F4DBB26.2060907@linux.vnet.ibm.com>
Date: Wed, 29 Feb 2012 11:14:06 +0530
From: "Srivatsa S. Bhat" <srivatsa.bhat@...ux.vnet.ibm.com>
To: Andrew Morton <akpm@...ux-foundation.org>
CC: Ingo Molnar <mingo@...e.hu>, Rusty Russell <rusty@...tcorp.com.au>,
Nick Piggin <npiggin@...nel.dk>,
linux-kernel <linux-kernel@...r.kernel.org>,
Alexander Viro <viro@...iv.linux.org.uk>,
Andi Kleen <ak@...ux.intel.com>, linux-fsdevel@...r.kernel.org
Subject: Re: [PATCH] cpumask: fix lg_lock/br_lock.
Hi Andrew,
On 02/29/2012 02:57 AM, Andrew Morton wrote:
> On Tue, 28 Feb 2012 09:43:59 +0100
> Ingo Molnar <mingo@...e.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)
> I do think the brlock code is sick, but Nick has turned into an ex-Nick
> and nobody works on it.
>
Regards,
Srivatsa S. Bhat
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists