[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20140206.211950.143290861607860665.davem@davemloft.net>
Date: Thu, 06 Feb 2014 21:19:50 -0800 (PST)
From: David Miller <davem@...emloft.net>
To: srivatsa.bhat@...ux.vnet.ibm.com
Cc: paulus@...ba.org, oleg@...hat.com, rusty@...tcorp.com.au,
peterz@...radead.org, tglx@...utronix.de,
akpm@...ux-foundation.org, mingo@...nel.org,
paulmck@...ux.vnet.ibm.com, tj@...nel.org, walken@...gle.com,
ego@...ux.vnet.ibm.com, linux@....linux.org.uk,
linux-kernel@...r.kernel.org, roy.qing.li@...il.com,
sasha.levin@...cle.com, cmetcalf@...era.com, netdev@...r.kernel.org
Subject: Re: [PATCH 50/51] net/core/flow.c: Fix CPU hotplug callback
registration
From: David Miller <davem@...emloft.net>
Date: Thu, 06 Feb 2014 20:39:21 -0800 (PST)
> From: "Srivatsa S. Bhat" <srivatsa.bhat@...ux.vnet.ibm.com>
> Date: Thu, 06 Feb 2014 03:43:46 +0530
>
>> Subsystems that want to register CPU hotplug callbacks, as well as perform
>> initialization for the CPUs that are already online, often do it as shown
>> below:
> ...
>> This is wrong, since it is prone to ABBA deadlocks involving the
>> cpu_add_remove_lock and the cpu_hotplug.lock (when running concurrently
>> with CPU hotplug operations).
>>
>> Instead, the correct and race-free way of performing the callback
>> registration is:
> ...
>> Fix the code in net/core/flow.c by using this latter form of callback
>> registration.
>>
>> Cc: "David S. Miller" <davem@...emloft.net>
>> Cc: Li RongQing <roy.qing.li@...il.com>
>> Cc: Sasha Levin <sasha.levin@...cle.com>
>> Cc: Andrew Morton <akpm@...ux-foundation.org>
>> Cc: Chris Metcalf <cmetcalf@...era.com>
>> Cc: netdev@...r.kernel.org
>> Signed-off-by: Srivatsa S. Bhat <srivatsa.bhat@...ux.vnet.ibm.com>
>
> Applied.
I just realized that this has a dependency not in the 'net'
tree, so I reverted and assume you will merge this with the
patch that provides the necessary interface(s).
Signed-off-by: David S. Miller <davem@...emloft.net>
--
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