Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932998AbYBUUtv (ORCPT ); Thu, 21 Feb 2008 15:49:51 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1764995AbYBUUtT (ORCPT ); Thu, 21 Feb 2008 15:49:19 -0500 Received: from mx1.redhat.com ([66.187.233.31]:45864 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1760393AbYBUUtJ (ORCPT ); Thu, 21 Feb 2008 15:49:09 -0500 From: Glauber Costa To: linux-kernel@vger.kernel.org Cc: akpm@linux-foundation.org, glommer@gmail.com, mingo@elte.hu, pzijlstr@redhat.com, arjan@infradead.org Subject: [PATCH 0/2] onlining cpus can break lockdep Date: Thu, 21 Feb 2008 17:40:54 -0300 Message-Id: <1203626456-3101-1-git-send-email-gcosta@redhat.com> X-Mailer: git-send-email 1.5.3.6 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 871 Lines: 23 Hi, While testing with hotplugging cpus today, I've came across a stack trace generated by lockdep. The reason for that is that do_boot_cpu() in smpboot_64.c ends up initializing a struct work_struct variable in the stack. These patches fix this by making it static. a per-cpu variable is choosen, since, to the best of my knowledge, nothing prevents two cpus going up at the same time, and so a single static c_idle won't do. I separated it in two patches to better isolate the change. The first patch just paves the way, by turning access to c_idle into pointer dereferences. The second one does the real work. Thanks -- 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/