Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753360Ab3JGXdb (ORCPT ); Mon, 7 Oct 2013 19:33:31 -0400 Received: from caramon.arm.linux.org.uk ([78.32.30.218]:40721 "EHLO caramon.arm.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751819Ab3JGXd2 (ORCPT ); Mon, 7 Oct 2013 19:33:28 -0400 Date: Tue, 8 Oct 2013 00:33:10 +0100 From: Russell King - ARM Linux To: Linus Torvalds Cc: Fengguang Wu , xen-devel@lists.xenproject.org, Linux Kernel Mailing List , Greg Kroah-Hartman Subject: Re: [xen] double fault: 0000 [#1] PREEMPT SMP DEBUG_PAGEALLOC Message-ID: <20131007233310.GA24844@n2100.arm.linux.org.uk> References: <20131006082340.GA24568@localhost> <20131007021118.GA27927@localhost> <20131007051038.GA9764@localhost> <20131007083505.GA22585@localhost> <20131007222925.GV12758@n2100.arm.linux.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20131007222925.GV12758@n2100.arm.linux.org.uk> User-Agent: Mutt/1.5.19 (2009-01-05) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 909 Lines: 18 On Mon, Oct 07, 2013 at 11:29:25PM +0100, Russell King - ARM Linux wrote: > However, due to the problems with x86, that's fallen on its head and I > have no solution to get better debugging out which works across all > architectures. I'm stumpted by this. The final attempt at trying to sort this may be to try allocating a struct at release time to contain a pointer to the kobject and the delayed work queue, and maybe a stack trace. The thing I worry about is whether we can allocate memory at that point. GFP_ATOMIC maybe? Should be a small enough structure that it shouldn't eat too much into the reserved pools. I won't be coding it up tonight though! -- 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/