From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752215AbdAYOZa (ORCPT ); Wed, 25 Jan 2017 09:25:30 -0500 Received: from merlin.infradead.org ([205.233.59.134]:54034 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752033AbdAYOZ3 (ORCPT ); Wed, 25 Jan 2017 09:25:29 -0500 Date: Wed, 25 Jan 2017 15:25:24 +0100 From: Peter Zijlstra To: Andrey Ryabinin , Alexander Potapenko , Dmitry Vyukov , linux-kernel@vger.kernel.org Cc: Steven Rostedt Subject: [PATCH] kasan: Respect /proc/sys/kernel/traceoff_on_warning Message-ID: <20170125142524.GQ6515@twins.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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 After much waiting I finally reproduced a KASAN issue, only to find my trace-buffer empty of useful information because it got spooled out :/ Make kasan_report honour the /proc/sys/kernel/traceoff_on_warning interface. Signed-off-by: Peter Zijlstra (Intel) --- mm/kasan/report.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/mm/kasan/report.c b/mm/kasan/report.c index b82b3e2..6ff7efc 100644 --- a/mm/kasan/report.c +++ b/mm/kasan/report.c @@ -300,6 +300,8 @@ void kasan_report(unsigned long addr, size_t size, if (likely(!kasan_report_enabled())) return; + disable_trace_on_warning(); + info.access_addr = (void *)addr; info.access_size = size; info.is_write = is_write;