linux-kernel - Re: [xen] double fault: 0000 [#1] PREEMPT SMP DEBUG

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20131007233310.GA24844@n2100.arm.linux.org.uk>
Date:	Tue, 8 Oct 2013 00:33:10 +0100
From:	Russell King - ARM Linux <linux@....linux.org.uk>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Fengguang Wu <fengguang.wu@...el.com>,
	xen-devel@...ts.xenproject.org,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: [xen] double fault: 0000 [#1] PREEMPT SMP DEBUG_PAGEALLOC

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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/