Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932191Ab3CLGlN (ORCPT ); Tue, 12 Mar 2013 02:41:13 -0400 Received: from mail-lb0-f182.google.com ([209.85.217.182]:63617 "EHLO mail-lb0-f182.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753653Ab3CLGlM (ORCPT ); Tue, 12 Mar 2013 02:41:12 -0400 MIME-Version: 1.0 In-Reply-To: <20130312061303.GB20037@mtj.dyndns.org> References: <20130307154907.GB29601@htj.dyndns.org> <20130312051215.GU14556@mtj.dyndns.org> <20130312052426.GV14556@mtj.dyndns.org> <20130312054028.GA20037@mtj.dyndns.org> <20130312061303.GB20037@mtj.dyndns.org> Date: Tue, 12 Mar 2013 14:41:10 +0800 Message-ID: Subject: Re: workqueue panic in 3.4 kernel From: Lei Wen To: Tejun Heo Cc: Thomas Gleixner , linux-kernel@vger.kernel.org, leiwen@marvell.com, wwang27@marvell.com Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 997 Lines: 25 On Tue, Mar 12, 2013 at 2:13 PM, Tejun Heo wrote: > On Tue, Mar 12, 2013 at 02:01:16PM +0800, Lei Wen wrote: >> I see... >> How about only check those workqueue structure not on stack? >> For current onstack usage is rare, and should be easier to check with. > > No, kzalloc is not required. The memory area can come from any source. > If you're interested in improving the debug situation, please stop > trying to do something impossible (you can't track lifetime of random > memory area without extra bookkeeping) try to find out why debugobj > didn't detect it (did you even enable it? either via > CONFIG_DEBUG_OBJECTS_ENABLE_DEFAULT or "debug_objects" boot param). > I see... Thanks for the detailed explanation! :) Thanks, Lei -- 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/