From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755909Ab1G0VwX (ORCPT ); Wed, 27 Jul 2011 17:52:23 -0400 Received: from www.linutronix.de ([62.245.132.108]:36121 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755882Ab1G0VwU (ORCPT ); Wed, 27 Jul 2011 17:52:20 -0400 Date: Wed, 27 Jul 2011 23:52:18 +0200 (CEST) From: Thomas Gleixner To: Yong Zhang cc: LKML , linux-rt-users , Peter Zijlstra , Ingo Molnar Subject: Re: migrate_disable() race with cpu hotplug? In-Reply-To: Message-ID: References: User-Agent: Alpine 2.02 (LFD 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 26 Jul 2011, Yong Zhang wrote: > When reading the code, I'm afraid there is a race between migrate_disable() > and cpu hotplug. A scenario will like below: > > CPU0 CPU1 > _cpu_down(); > cpu_unplug_begin(); > wait_for_completion() > sync_unplug_thread(); > complete(); > race_window? /* > * migrate_disable() will > * not take effect since > * hotplug is in progress > */ Rightfully so. The caller will just block on the cpu_hotplug.lock mutex until the unplug operation will be done. Thanks, tglx