Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753414AbbKWQh6 (ORCPT ); Mon, 23 Nov 2015 11:37:58 -0500 Received: from pandora.arm.linux.org.uk ([78.32.30.218]:50519 "EHLO pandora.arm.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751672AbbKWQh4 (ORCPT ); Mon, 23 Nov 2015 11:37:56 -0500 Date: Mon, 23 Nov 2015 16:37:50 +0000 From: Russell King - ARM Linux To: Willy Tarreau Cc: Arnd Bergmann , linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, josh@joshtriplett.org Subject: Re: [RFC] asm-generic: default BUG_ON(x) to "if(x) BUG()" Message-ID: <20151123163750.GT8644@n2100.arm.linux.org.uk> References: <5868782.RxZY0W5S4d@wuerfel> <20151123163359.GC768@1wt.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20151123163359.GC768@1wt.eu> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 850 Lines: 18 On Mon, Nov 23, 2015 at 05:33:59PM +0100, Willy Tarreau wrote: > I think you could do better by simply calling panic("BUG!") instead as > BUG() does. It will avoid the printk() call and pushing the file/line > number onto the stack. It will also probably not inflate the rodata this > way. Does that not depend on the architectures BUG() implementation? If an architecture implements it as a signalling illegal instruction and a lookup table, changing it to be a panic() would probably be more code. -- FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up according to speedtest.net. -- 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/