Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752582AbbFHII2 (ORCPT ); Mon, 8 Jun 2015 04:08:28 -0400 Received: from mail-vn0-f48.google.com ([209.85.216.48]:43711 "EHLO mail-vn0-f48.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751190AbbFHIIS (ORCPT ); Mon, 8 Jun 2015 04:08:18 -0400 MIME-Version: 1.0 In-Reply-To: <557546E6.5030304@ahsoftware.de> References: <1433721270-9182-1-git-send-email-lou_langholtz@me.com> <20150608000007.GA3543@mtj.duckdns.org> <20150608071215.GA369@gmail.com> <557546E6.5030304@ahsoftware.de> Date: Mon, 8 Jun 2015 10:08:17 +0200 Message-ID: Subject: Re: [PATCH] debug: Deprecate BUG_ON() use in new code, introduce CRASH_ON() From: Richard Weinberger To: Alexander Holler Cc: Ingo Molnar , Linus Torvalds , Tejun Heo , Louis Langholtz , Linux Kernel Mailing List , Trivial patch monkey , Rusty Russell , Andrew Morton , Peter Zijlstra , Thomas Gleixner Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 769 Lines: 27 On Mon, Jun 8, 2015 at 9:40 AM, Alexander Holler wrote: > Am 08.06.2015 um 09:12 schrieb Ingo Molnar: >> >> >> * Linus Torvalds wrote: >> >>> Stop with the random BUG_ON() additions. >> >> >> Yeah, so I propose the attached patch which attempts to resist new >> BUG_ON() >> additions. > > > As this reminded me at flame I received once from a maintainer because I > wanted to avoid a desastrous memory corruption by using a BUG_ON(). Reference? -- Thanks, //richard -- 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/