From: Steven Rostedt <rostedt@goodmis.org>
To: Borislav Petkov <bp@alien8.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
"Theodore Ts'o" <tytso@mit.edu>, Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Peter Hurley <peter@hurleysoftware.com>
Subject: Re: [RFC][PATCH] tracing: Print nasty banner when trace_printk() is in use
Date: Wed, 28 May 2014 13:41:20 -0400 [thread overview]
Message-ID: <20140528134120.3328605e@gandalf.local.home> (raw)
In-Reply-To: <20140528172618.GB17220@pd.tnic>
On Wed, 28 May 2014 19:26:18 +0200
Borislav Petkov <bp@alien8.de> wrote:
> On Wed, May 28, 2014 at 01:14:40PM -0400, Steven Rostedt wrote:
> > Here's the banner:
> >
> > ****************************************
> > ** NOTICE NOTICE NOTICE NOTICE NOTICE **
> > ** trace_printk() being used. **
> > ** Allocating extra memory for it **
> > ****************************************
> >
> > Hmm, maybe I should add "Not for production use" to scare people even
> > more?
>
> Yes, and at least some swearing - this is the linux kernel for
> chrissake. Or are you gone soft too?
>
Going soft? Nah, you know me. I never swear, so how could not swearing
cause me to go soft :-)
Perhaps a:
*********************************************************
** NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE **
** **
** trace_printk() being used. **
** Allocating extra memory for it **
** **
** This means that this is a DEBUG kernel and it is **
** unsafe for production use. **
** **
** If you see this message and you are not debugging **
** the kernel, report this immediately to your vendor! **
** **
** NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE **
*********************************************************
Maybe that will work?
-- Steve
next prev parent reply other threads:[~2014-05-28 17:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-28 17:14 Steven Rostedt
2014-05-28 17:22 ` Peter Zijlstra
2014-05-28 17:37 ` Steven Rostedt
2014-05-28 17:26 ` Borislav Petkov
2014-05-28 17:41 ` Steven Rostedt [this message]
2014-05-30 6:07 ` Olaf Titz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140528134120.3328605e@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peter@hurleysoftware.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®