[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230405135813.735507007@goodmis.org>
Date:   Wed, 05 Apr 2023 09:58:13 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     linux-kernel@...r.kernel.org
Cc:     Masami Hiramatsu <mhiramat@...nel.org>,
        Mark Rutland <mark.rutland@....com>,
        Andrew Morton <akpm@...ux-foundation.org>
Subject: [for-linus][PATCH 0/3] tracing: More fixes for 6.3
- Fix boot up snapshot code:
  Boot snapshots were triggering when not even asked for on the
  kernel command line. This was caused by two bugs.
  1) It would trigger a snapshot on any instance if one was created
     from the kernel command line.
  2) The error handling would only affect the top level instance.
     So the fact that a snapshot was done on a instance that didn't
     allocate a buffer triggered a warning written into the top level
     buffer, and worse yet, disabled the top level buffer.
- Fix memory leak that was caused when an error was logged in a
  trace buffer instance, and then the buffer instance was removed.
  The allocated error log messages still need to be freed.
  git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git
trace/urgent
Head SHA1: 3357c6e429643231e60447b52ffbb7ac895aca22
Steven Rostedt (Google) (3):
      tracing: Have tracing_snapshot_instance_cond() write errors to the appropriate instance
      tracing: Fix ftrace_boot_snapshot command line logic
      tracing: Free error logs of tracing instances
----
 kernel/trace/trace.c | 28 +++++++++++++++-------------
 1 file changed, 15 insertions(+), 13 deletions(-)
Powered by blists - more mailing lists
 
