From mboxrd@z Thu Jan 1 00:00:00 1970 From: Balbir Singh Subject: Re: per_cpu_counter_sum lockdep warning Date: Wed, 04 Jun 2008 10:26:14 +0530 Message-ID: <4846206E.2070507@linux.vnet.ibm.com> References: <48460B94.8050000@linux.vnet.ibm.com> <20080604035954.GE3549@parisc-linux.org> Reply-To: balbir@linux.vnet.ibm.com Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: linux-fsdevel@vger.kernel.org, linux kernel mailing list To: Matthew Wilcox Return-path: Received: from e28smtp04.in.ibm.com ([59.145.155.4]:42971 "EHLO e28smtp04.in.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751092AbYFDE5u (ORCPT ); Wed, 4 Jun 2008 00:57:50 -0400 In-Reply-To: <20080604035954.GE3549@parisc-linux.org> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: > > Some percpu counters are supposed to be used from interrupt context. > These are created with percpu_counter_init_irq. Others are not and > should be created with percpu_counter_init. It seems like someone's > made a mess of that rule. This is likely to be a driver, IMO. Perhaps > you could work on tracking this down? > Sorry for the noise. It was patch I had applied on my tree, not yet in mainline. The explanation though did help me find and fix the problem. -- Warm Regards, Balbir Singh Linux Technology Center IBM, ISTL