From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steven Rostedt Subject: Re: [RFC PATCH for 4.21 03/16] mm: Replace BUG_ON() by WARN_ON() in vm_unmap_ram() Date: Thu, 1 Nov 2018 14:46:23 -0400 Message-ID: <20181101144623.61d43102@gandalf.local.home> References: <20181101095844.24462-1-mathieu.desnoyers@efficios.com> <20181101095844.24462-4-mathieu.desnoyers@efficios.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Thomas Gleixner Cc: Mathieu Desnoyers , Peter Zijlstra , "Paul E . McKenney" , Boqun Feng , linux-kernel@vger.kernel.org, linux-api@vger.kernel.org, Andy Lutomirski , Dave Watson , Paul Turner , Andrew Morton , Russell King , Ingo Molnar , "H . Peter Anvin" , Andi Kleen , Chris Lameter , Ben Maurer , Josh Triplett , Linus Torvalds , Catalin Marinas , Will Deacon List-Id: linux-api@vger.kernel.org On Thu, 1 Nov 2018 13:21:12 +0100 (CET) Thomas Gleixner wrote: > Mathieu, > > On Thu, 1 Nov 2018, Mathieu Desnoyers wrote: > > > It is encouraged to warn and return rather than use BUG_ON() when > > the condition can be recovered from in ways that are more graceful than > > halting the whole system. > > You're failing to desribe how that graceful recovery works. > I think the graceful recovery is to simply return: if (WARN_ON(cond)) return; is better than just BUG_ON(cond); As that's what Linus made pretty clear at the Maintainer's Summit. -- Steve