Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752413AbbFHHNG (ORCPT ); Mon, 8 Jun 2015 03:13:06 -0400 Received: from mail-wi0-f173.google.com ([209.85.212.173]:34831 "EHLO mail-wi0-f173.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752430AbbFHHMU (ORCPT ); Mon, 8 Jun 2015 03:12:20 -0400 Date: Mon, 8 Jun 2015 09:12:15 +0200 From: Ingo Molnar To: Linus Torvalds Cc: Tejun Heo , Louis Langholtz , Linux Kernel Mailing List , trivial@kernel.org, Rusty Russell , Andrew Morton , Peter Zijlstra , Thomas Gleixner Subject: [PATCH] debug: Deprecate BUG_ON() use in new code, introduce CRASH_ON() Message-ID: <20150608071215.GA369@gmail.com> References: <1433721270-9182-1-git-send-email-lou_langholtz@me.com> <20150608000007.GA3543@mtj.duckdns.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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: 3086 Lines: 85 * 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. Thanks, Ingo ================================> >From 724052923fbae2e3a14e0b9383c89b18217d817f Mon Sep 17 00:00:00 2001 From: Ingo Molnar Date: Mon, 8 Jun 2015 09:01:43 +0200 Subject: [PATCH] debug: Deprecate BUG_ON() use in new code, introduce CRASH_ON() So people still keep adding random BUG_ON() lines, as a mistaken practice to put asserts that will never trigger, into supposedly perfect kernel code. So such BUG_ON()s should either not be added, because the code is truly perfect, or if there's a chance that it's imperfect, use WARN_ON() instead and limp along, in the hope of getting some debug information back from the user. Using BUG_ON() will just hang or reboot most systems, with no useful feedback provided. It's as user hostile as it gets. Add a checkpatch rule that warns against new BUG_ON() uses: WARNING: Using BUG_ON() is generally wrong, use WARN_ON() instead - or CRASH_ON() if the kernel absolutely must crash. CRASH_ON() can be used in code that must absolutely crash right then, in the very rare case where there's no way the system can be allowed to continue execution. It should be used sparingly, and its name will hopefully achieve this. Signed-off-by: Ingo Molnar --- include/asm-generic/bug.h | 7 +++++++ scripts/checkpatch.pl | 6 ++++++ 2 files changed, 13 insertions(+) diff --git a/include/asm-generic/bug.h b/include/asm-generic/bug.h index 630dd2372238..c6424723277b 100644 --- a/include/asm-generic/bug.h +++ b/include/asm-generic/bug.h @@ -165,6 +165,13 @@ extern void warn_slowpath_null(const char *file, const int line); #define WARN_TAINT(condition, taint, format...) WARN(condition, format) #define WARN_TAINT_ONCE(condition, taint, format...) WARN(condition, format) +/* + * BUG_ON() is deprecated, use either one of the WARN_ON() variants, + * or if it's absolutely unavoidable to crash the system due to + * some grave condition, use CRASH_ON(): + */ +#define CRASH_ON(condition) BUG_ON(condition) + #endif /* diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl index 89b1df4e72ab..6e0887057398 100755 --- a/scripts/checkpatch.pl +++ b/scripts/checkpatch.pl @@ -5414,6 +5414,12 @@ sub process { "Using $1 should generally have parentheses around the comparison\n" . $herecurr); } +# check for use of BUG_ON() + if ($line =~ /\bBUG_ON\s*\(/) { + WARN("BUG_ON", + "Using BUG_ON() is generally wrong, use WARN_ON() instead - or CRASH_ON() if the kernel absolutely must crash.\n" . $herecurr); + } + # whine mightly about in_atomic if ($line =~ /\bin_atomic\s*\(/) { if ($realfile =~ m@^drivers/@) { -- 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/