From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756905Ab3CFKVG (ORCPT ); Wed, 6 Mar 2013 05:21:06 -0500 Received: from mail-ee0-f43.google.com ([74.125.83.43]:39468 "EHLO mail-ee0-f43.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752942Ab3CFKVC (ORCPT ); Wed, 6 Mar 2013 05:21:02 -0500 Date: Wed, 6 Mar 2013 11:20:57 +0100 From: Ingo Molnar To: Ming Lei Cc: Peter Zijlstra , Ingo Molnar , Linux Kernel Mailing List Subject: Re: lockdep: access percpu variable too early Message-ID: <20130306102057.GB6587@gmail.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Ming Lei wrote: > Hi, > > The percpu variables of 'lockdep_stats' and 'cpu_lock_stat' may be accessed before > percpu area is brought up in case of CONFIG_DEBUG_LOCKDEP/CONFIG_LOCK_STAT, so > these variables in non-boot CPUs will be initialized incorrectly. What's the practical effect of it? Do we copy the value from the boot CPU and thus the secondary CPUs start with slightly increased stats? Thanks, Ingo