linux-kernel - Re: [PATCH] kasan: Respect /proc/sys/kernel/traceoff_on

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20170125143532.GR6515@twins.programming.kicks-ass.net>
Date:   Wed, 25 Jan 2017 15:35:32 +0100
From:   Peter Zijlstra <peterz@...radead.org>
To:     Alexander Potapenko <glider@...gle.com>
Cc:     Andrey Ryabinin <aryabinin@...tuozzo.com>,
        Dmitry Vyukov <dvyukov@...gle.com>,
        LKML <linux-kernel@...r.kernel.org>,
        Steven Rostedt <rostedt@...dmis.org>
Subject: Re: [PATCH] kasan: Respect /proc/sys/kernel/traceoff_on_warning

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.