Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932192AbbFHTfb (ORCPT ); Mon, 8 Jun 2015 15:35:31 -0400 Received: from mail-wi0-f181.google.com ([209.85.212.181]:34366 "EHLO mail-wi0-f181.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753511AbbFHTfT (ORCPT ); Mon, 8 Jun 2015 15:35:19 -0400 Date: Mon, 8 Jun 2015 21:35:14 +0200 From: Ingo Molnar To: Alexander Holler Cc: Richard Weinberger , Linus Torvalds , Tejun Heo , Louis Langholtz , Linux Kernel Mailing List , Trivial patch monkey , Rusty Russell , Andrew Morton , Peter Zijlstra , Thomas Gleixner , Greg Kroah-Hartman Subject: Re: [PATCH] debug: Deprecate BUG_ON() use in new code, introduce CRASH_ON() Message-ID: <20150608193514.GA13053@gmail.com> References: <20150608000007.GA3543@mtj.duckdns.org> <20150608071215.GA369@gmail.com> <557546E6.5030304@ahsoftware.de> <5575558E.5070706@ahsoftware.de> <20150608090509.GA19160@gmail.com> <55755D6F.3030201@ahsoftware.de> <20150608112702.GA20511@gmail.com> <5575D9C4.50204@ahsoftware.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5575D9C4.50204@ahsoftware.de> 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: 1360 Lines: 40 * Alexander Holler wrote: > Am 08.06.2015 um 13:27 schrieb Ingo Molnar: > > > >* Alexander Holler wrote: > > > >>>I am pretty certain that Greg would have applied such a patch in an eye blink. > >> > >>As you've said it, *probably*. But such a simple exit path as you're proposing > >>doesn't always exist. [...] > > > >As I said it's case by case. I discussed your example (which was a deficient patch > >for multiple reasons) but we'd be wasting everyone's time by discussion > >hypothethical situations. > > Sure it was a deficient patch, but still better than what existed for a year > long in the kernel [...] ... but it was still worse than the simple solution I suggested: if (WARN_ON_ONCE(port->itty)) return; again, the BUG_ON() you wanted to introduce was wrong on multiple grounds, then and now. Why are you still arguing about this? > I just want to make clear that a brutforce slogan like BUG_ON is bad is bad, I pointed out specific cases where a BUG_ON() is the right solution. They are rare. Stop misrepresenting my words. Thanks, Ingo -- 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/