Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760438AbZFWPbj (ORCPT ); Tue, 23 Jun 2009 11:31:39 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1758339AbZFWP3w (ORCPT ); Tue, 23 Jun 2009 11:29:52 -0400 Received: from lanfw001a.cxnet.dk ([87.72.215.196]:49565 "EHLO lanfw001a.cxnet.dk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754354AbZFWP3s (ORCPT ); Tue, 23 Jun 2009 11:29:48 -0400 From: Jesper Dangaard Brouer Subject: [PATCH 08/10] edac_core: Uses call_rcu() and its own wait_for_completion scheme. To: "David S. Miller" Cc: Jesper Dangaard Brouer , "Paul E. McKenney" , netdev@vger.kernel.org, linux-kernel@vger.kernel.org, dougthompson@xmission.com, bluesmoke-devel@lists.sourceforge.net, axboe@kernel.dk, "Patrick McHardy" , christine.caulfield@googlemail.com, Trond.Myklebust@netapp.com, linux-wireless@vger.kernel.org, johannes@sipsolutions.net, yoshfuji@linux-ipv6.org, shemminger@linux-foundation.org, linux-nfs@vger.kernel.org, bfields@fieldses.org, neilb@suse.de, linux-ext4@vger.kernel.org, tytso@mit.edu, adilger@sun.com, netfilter-devel@vger.kernel.org Date: Tue, 23 Jun 2009 17:04:34 +0200 Message-ID: <20090623150434.22490.18824.stgit@localhost> In-Reply-To: <20090623150330.22490.87327.stgit@localhost> References: <20090623150330.22490.87327.stgit@localhost> User-Agent: StGIT/0.14.2 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2666 Lines: 73 Module edac_core.ko uses call_rcu() callbacks in edac_device.c, edac_mc.c and edac_pci.c. They all uses a wait_for_completion scheme, but this scheme it not 100% safe on multiple CPUs. See the _rcu_barrier() implementation which explains why extra precausion is needed. The patch adds a comment about rcu_barrier() and as a precausion calls rcu_barrier(). A maintainer needs to look at removing the wait_for_completion code. Signed-off-by: Jesper Dangaard Brouer --- drivers/edac/edac_device.c | 5 +++++ drivers/edac/edac_mc.c | 5 +++++ drivers/edac/edac_pci.c | 5 +++++ 3 files changed, 15 insertions(+), 0 deletions(-) diff --git a/drivers/edac/edac_device.c b/drivers/edac/edac_device.c index b02a6a6..5e831c9 100644 --- a/drivers/edac/edac_device.c +++ b/drivers/edac/edac_device.c @@ -373,6 +373,11 @@ static void del_edac_device_from_global_list(struct edac_device_ctl_info init_completion(&edac_device->removal_complete); call_rcu(&edac_device->rcu, complete_edac_device_list_del); wait_for_completion(&edac_device->removal_complete); + + /* hawk@comx.dk 2009-06-22: I think that rcu_barrier() should + * be used instead of wait_for_completion, because + * rcu_barrier() take multiple CPUs into account */ + rcu_barrier(); } /* diff --git a/drivers/edac/edac_mc.c b/drivers/edac/edac_mc.c index 335b7eb..edcce41 100644 --- a/drivers/edac/edac_mc.c +++ b/drivers/edac/edac_mc.c @@ -428,6 +428,11 @@ static void del_mc_from_global_list(struct mem_ctl_info *mci) init_completion(&mci->complete); call_rcu(&mci->rcu, complete_mc_list_del); wait_for_completion(&mci->complete); + + /* hawk@comx.dk 2009-06-22: I think that rcu_barrier() should + * be used instead of wait_for_completion, because + * rcu_barrier() take multiple CPUs into account */ + rcu_barrier(); } /** diff --git a/drivers/edac/edac_pci.c b/drivers/edac/edac_pci.c index 30b585b..d0eb8c9 100644 --- a/drivers/edac/edac_pci.c +++ b/drivers/edac/edac_pci.c @@ -188,6 +188,11 @@ static void del_edac_pci_from_global_list(struct edac_pci_ctl_info *pci) init_completion(&pci->complete); call_rcu(&pci->rcu, complete_edac_pci_list_del); wait_for_completion(&pci->complete); + + /* hawk@comx.dk 2009-06-22: I think that rcu_barrier() should + * be used instead of wait_for_completion, because + * rcu_barrier() take multiple CPUs into account */ + rcu_barrier(); } #if 0 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/