All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vlastimil Babka <vbabka@suse.cz>
To: Steven Rostedt <rostedt@goodmis.org>, linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	stable@vger.kernel.org
Subject: Re: [for-next][PATCH 1/2] tracing: Fix trace_printk() to print when not using bprintk()
Date: Wed, 23 Mar 2016 15:13:22 +0100	[thread overview]
Message-ID: <56F2A482.1010302@suse.cz> (raw)
In-Reply-To: <20160323122508.858050620@goodmis.org>

On 03/23/2016 01:24 PM, Steven Rostedt wrote:
> From: "Steven Rostedt (Red Hat)" <rostedt@goodmis.org>
>
> The trace_printk() code will allocate extra buffers if the compile detects
> that a trace_printk() is used. To do this, the format of the trace_printk()
> is saved to the __trace_printk_fmt section, and if that section is bigger
> than zero, the buffers are allocated (along with a message that this has
> happened).
>
> If trace_printk() uses a format that is not a constant, and thus something
> not guaranteed to be around when the print happens, the compiler optimizes
> the fmt out, as it is not used, and the __trace_printk_fmt section is not
> filled. This means the kernel will not allocate the special buffers needed
> for the trace_printk() and the trace_printk() will not write anything to the
> tracing buffer.
>
> Adding a "__used" to the variable in the __trace_printk_fmt section will
> keep it around, even though it is set to NULL. This will keep the string
> from being printed in the debugfs/tracing/printk_formats section as it is
> not needed.
>
> Reported-by: Vlastimil Babka <vbabka@suse.cz>
> Fixes: 07d777fe8c398 "tracing: Add percpu buffers for trace_printk()"
> Cc: stable@vger.kernel.org # v3.5+
> Signed-off-by: Steven Rostedt <rostedt@goodmis.org>

Tested-by: Vlastimil Babka <vbabka@suse.cz>

Thanks!

  reply	other threads:[~2016-03-23 14:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-23 12:24 [for-next][PATCH 0/2] tracing: Some last minute changes before I push for 4.6 Steven Rostedt
2016-03-23 12:24 ` [for-next][PATCH 1/2] tracing: Fix trace_printk() to print when not using bprintk() Steven Rostedt
2016-03-23 14:13   ` Vlastimil Babka [this message]
2016-03-23 12:24 ` [for-next][PATCH 2/2] tracing: Record and show NMI state Steven Rostedt

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=56F2A482.1010302@suse.cz \
    --to=vbabka@suse.cz \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=stable@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.