[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200624120408.12c8fa0d@oasis.local.home>
Date: Wed, 24 Jun 2020 12:04:08 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Nicolas Boichat <drinkcat@...omium.org>
Cc: linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...hat.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Kees Cook <keescook@...omium.org>,
Jason Gunthorpe <jgg@...pe.ca>,
Daniel Vetter <daniel.vetter@...ll.ch>,
Peter Zijlstra <peterz@...radead.org>,
Vinod Koul <vkoul@...nel.org>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Alexey Dobriyan <adobriyan@...il.com>,
Tiezhu Yang <yangtiezhu@...ngson.cn>,
Thomas Gleixner <tglx@...utronix.de>,
"Guilherme G . Piccoli" <gpiccoli@...onical.com>,
Will Deacon <will@...nel.org>, dianders@...omium.org,
groeck@...omium.org
Subject: Re: [PATCH] kernel/trace: Add TRACING_ALLOW_PRINTK config option
On Wed, 24 Jun 2020 16:45:24 +0800
Nicolas Boichat <drinkcat@...omium.org> wrote:
> trace_printk is only meant as a debugging tool, and should never be
> compiled into production code without source code changes, as
> indicated by the warning that shows up on boot if any trace_printk
> is called:
> ** NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE **
> ** **
> ** trace_printk() being used. Allocating extra memory. **
> ** **
> ** This means that this is a DEBUG kernel and it is **
> ** unsafe for production use. **
>
> If this option is set to n, the kernel will generate a build-time
> error if trace_printk is used.
>
> Signed-off-by: Nicolas Boichat <drinkcat@...omium.org>
Interesting. Note, this will prevent modules with trace_printk from
being loaded as well.
-- Steve
Powered by blists - more mailing lists