mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: [for-next][PATCH 1/3] ftrace: Decrement count for dyn_ftrace_total_info for init functions
Date: Thu, 06 Jul 2017 08:28:01 -0400	[thread overview]
Message-ID: <20170706122848.197748260@goodmis.org> (raw)
In-Reply-To: <20170706122800.705318130@goodmis.org>

[-- Attachment #1: 0001-ftrace-Decrement-count-for-dyn_ftrace_total_info-for.patch --]
[-- Type: text/plain, Size: 803 bytes --]

From: "Steven Rostedt (VMware)" <rostedt@goodmis.org>

Init boot up functions may be traced, but they are also freed when the
kernel finishes booting. These are removed from the ftrace tables, and the
debug variable for dyn_ftrace_total_info needs to reflect that as well.

Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
---
 kernel/trace/ftrace.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/kernel/trace/ftrace.c b/kernel/trace/ftrace.c
index 2c79630cd267..e392f750a1cf 100644
--- a/kernel/trace/ftrace.c
+++ b/kernel/trace/ftrace.c
@@ -5825,6 +5825,7 @@ void __init ftrace_free_init_mem(void)
 		if (!rec)
 			continue;
 		pg->index--;
+		ftrace_update_tot_cnt--;
 		if (!pg->index) {
 			*last_pg = pg->next;
 			order = get_count_order(pg->size / ENTRIES_PER_PAGE);
-- 
2.10.2

  reply	other threads:[~2017-07-06 12:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-06 12:28 [for-next][PATCH 0/3] tracing: Last minute updates for 4.13 Steven Rostedt
2017-07-06 12:28 ` Steven Rostedt [this message]
2017-07-06 12:28 ` [for-next][PATCH 2/3] ftrace: Fix regression with module command in stack_trace_filter Steven Rostedt
2017-07-06 12:28 ` [for-next][PATCH 3/3] ftrace: Test for NULL iter->tr in regex for stack_trace_filter changes 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=20170706122848.197748260@goodmis.org \
    --to=rostedt@goodmis.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@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 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®