public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Ingo Molnar <mingo@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Tom Zanussi <tom.zanussi@linux.intel.com>
Subject: [PATCH 0/6] [GIT PULL] tracing: Various minor fixes
Date: Thu, 24 Aug 2017 10:21:43 -0400	[thread overview]
Message-ID: <20170824142143.110862355@goodmis.org> (raw)


Linus,

Various bug fixes:

 - Two small memory leaks in error paths.

 - A missed return error code on an error path.

 - A fix to check the tracing ring buffer CPU when it doesn't
   exist (caused by setting maxcpus on the command line that is less
   than the actual number of CPUs, and then onlining them manually).

 - A fix to have the reset of boot tracers called by lateinit_sync()
   instead of just lateinit(). As some of the tracers register via
   lateinit(), and if the clear happens before the tracer is registered,
   it will never start even though it was told to via the kernel command
   line.

Please pull the latest trace-v4.13-rc3 tree, which can be found at:


  git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
trace-v4.13-rc3

Tag SHA1: 6826d804a3ff83a1da1bb9964234f3b306f28449
Head SHA1: 8b0db1a5bdfcee0dbfa89607672598ae203c9045


Chunyu Hu (1):
      tracing: Fix kmemleak in tracing_map_array_free()

Dan Carpenter (1):
      tracing: Missing error code in tracer_alloc_buffers()

Steven Rostedt (VMware) (4):
      tracing: Call clear_boot_tracer() at lateinit_sync
      ring-buffer: Have ring_buffer_alloc_read_page() return error on offline CPU
      ftrace: Check for null ret_stack on profile function graph entry function
      tracing: Fix freeing of filter in create_filter() when set_str is false

----
 kernel/trace/ftrace.c                |  4 ++++
 kernel/trace/ring_buffer.c           | 14 +++++++++-----
 kernel/trace/ring_buffer_benchmark.c |  2 +-
 kernel/trace/trace.c                 | 19 +++++++++++++------
 kernel/trace/trace_events_filter.c   |  4 ++++
 kernel/trace/tracing_map.c           | 11 +++++++----
 6 files changed, 38 insertions(+), 16 deletions(-)

             reply	other threads:[~2017-08-24 14:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-24 14:21 Steven Rostedt [this message]
2017-08-24 14:21 ` [PATCH 1/6] tracing: Call clear_boot_tracer() at lateinit_sync Steven Rostedt
2017-08-24 14:21 ` [PATCH 2/6] tracing: Missing error code in tracer_alloc_buffers() Steven Rostedt
2017-08-24 14:21 ` [PATCH 3/6] ring-buffer: Have ring_buffer_alloc_read_page() return error on offline CPU Steven Rostedt
2017-08-24 14:21 ` [PATCH 4/6] ftrace: Check for null ret_stack on profile function graph entry function Steven Rostedt
2017-08-24 14:21 ` [PATCH 5/6] tracing: Fix kmemleak in tracing_map_array_free() Steven Rostedt
2017-08-24 14:21 ` [PATCH 6/6] tracing: Fix freeing of filter in create_filter() when set_str is false 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=20170824142143.110862355@goodmis.org \
    --to=rostedt@goodmis.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=tom.zanussi@linux.intel.com \
    --cc=torvalds@linux-foundation.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