From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sergey Senozhatsky Subject: Re: [RFC PATCH for 4.21 04/16] mm: Introduce vm_map_user_ram, vm_unmap_user_ram Date: Thu, 18 Oct 2018 00:34:08 +0900 Message-ID: <20181017153408.GB426@tigerII.localdomain> References: <20181010191936.7495-1-mathieu.desnoyers@efficios.com> <20181010191936.7495-5-mathieu.desnoyers@efficios.com> <20181016143016.10da89bd@gandalf.local.home> <20181017002722.GA1068@jagdpanzerIV> <1051015468.759.1539788401096.JavaMail.zimbra@efficios.com> <2060193272.771.1539788641739.JavaMail.zimbra@efficios.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <2060193272.771.1539788641739.JavaMail.zimbra@efficios.com> Sender: linux-kernel-owner@vger.kernel.org To: Mathieu Desnoyers Cc: Sergey Senozhatsky , rostedt , Peter Zijlstra , "Paul E. McKenney" , Boqun Feng , linux-kernel , linux-api , Thomas Gleixner , 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 List-Id: linux-api@vger.kernel.org On (10/17/18 11:04), Mathieu Desnoyers wrote: > >> > >>> if (WARN_ON(x)) > >>> return; > >> > >> Given that this somewhat MM-related, I'd may be say VM_WARN_ON(). > > I notice that VM_WARN_ON() casts the result of WARN_ON() to (void), so it > cannot be used in a if () statement. > > VM_WARN_ON() will only warn if CONFIG_DEBUG_VM is set. > > Is it really what we want ? Oh, indeed... Sorry, I forgot that they cast WANR_ON() return to void. Let's do what Steven suggested. -ss