From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from pandora.arm.linux.org.uk (pandora.arm.linux.org.uk [IPv6:2001:4d48:ad52:3201:214:fdff:fe10:1be6]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 37DDB1A12CD for ; Tue, 24 Feb 2015 21:44:47 +1100 (AEDT) Date: Tue, 24 Feb 2015 10:43:40 +0000 From: Russell King - ARM Linux To: Arjan van de Ven Subject: Re: [PATCH 0/7] Serialise oopses, BUGs, WARNs, dump_stack, soft lockups and hard lockups Message-ID: <20150224104339.GT8656@n2100.arm.linux.org.uk> References: <1424748634-9153-1-git-send-email-anton@samba.org> <20150224063513.GA15387@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: Sender: Russell King - ARM Linux Cc: Don Zickus , X86 ML , Thomas Gleixner , Peter Zijlstra , "H. Peter Anvin" , LKML , Steven Rostedt , Linus Torvalds , Ingo Molnar , Paul Mackerras , Anton Blanchard , Andrew Morton , Arjan van de Ven , ppc-dev , Ingo Molnar , sam.bobroff@au1.ibm.com, linux-arm-kernel@lists.infradead.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Tue, Feb 24, 2015 at 01:39:46AM -0800, Arjan van de Ven wrote: > one of the question is if you want to serialize, or if you just want > to label. If you take a cookie (could just be a monotonic increasing > number) at the start of the oops and then prefix/postfix the stack > printing with that number, you don't serialize (risk of locking up), > but you can pretty trivially see which line came from where.. > if you do the monotonic increasing number approach, you even get an > ordering out of it. it does mean changing the dump_stack() and co > function fingerprint to take an extra argument, but that is not TOO > insane. I like that idea, but it relies on ensuring that each line is printed by one printk() statement - which in itself is a good idea. I'd actually like a version of print_hex_dump() which we could use for stack and code dumping - the existing print_hex_dump() assumes that it's fine to dereference the pointer, whereas for stack and code dumping, we can't always make that assumption. That's a separate issue though. -- FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up according to speedtest.net.