From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751152AbdAYOfi (ORCPT ); Wed, 25 Jan 2017 09:35:38 -0500 Received: from merlin.infradead.org ([205.233.59.134]:54058 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750729AbdAYOfh (ORCPT ); Wed, 25 Jan 2017 09:35:37 -0500 Date: Wed, 25 Jan 2017 15:35:32 +0100 From: Peter Zijlstra To: Alexander Potapenko Cc: Andrey Ryabinin , Dmitry Vyukov , LKML , Steven Rostedt Subject: Re: [PATCH] kasan: Respect /proc/sys/kernel/traceoff_on_warning Message-ID: <20170125143532.GR6515@twins.programming.kicks-ass.net> References: <20170125142524.GQ6515@twins.programming.kicks-ass.net> <20170125142852.GE6536@twins.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23.1 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jan 25, 2017 at 03:32:11PM +0100, Alexander Potapenko wrote: > > @@ -300,6 +301,8 @@ void kasan_report(unsigned long addr, size_t size, > > if (likely(!kasan_report_enabled())) > > return; > > > > + disable_trace_on_warning(); > > + > Who is going to enable tracing back after we're done? The user.. > Note that KASAN errors are not fatal, and the first one may possibly > occur quite early. WARN*() isn't fatal either, and it does the same thing. Note that traceoff_on_warning is default disabled. You have to explicitly request this.