All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: [for-linus][PATCH 0/3] tracing: Minor fixes for 6.5-rc2
Date: Sun, 23 Jul 2023 16:06:23 -0400	[thread overview]
Message-ID: <20230723200623.034313147@goodmis.org> (raw)

Tracing fixes for 6.5-rc2:

- Swapping the ring buffer for snapshotting (for things like irqsoff)
  can crash if the ring buffer is being resized. Disable swapping
  when this happens. The missed swap will be reported to the tracer.

- Report error if the histogram fails to be created due to an error in
  adding a histogram variable, in event_hist_trigger_parse().

- Remove unused declaration of tracing_map_set_field_descr().


Chen Lin (1):
      ring-buffer: Do not swap cpu_buffer during resize process

Mohamed Khalfella (1):
      tracing/histograms: Return an error if we fail to add histogram to hist_vars list

YueHaibing (1):
      tracing: Remove unused extern declaration tracing_map_set_field_descr()

----
 kernel/trace/ring_buffer.c       | 14 +++++++++++++-
 kernel/trace/trace.c             |  3 ++-
 kernel/trace/trace_events_hist.c |  3 ++-
 kernel/trace/tracing_map.h       |  4 ----
 4 files changed, 17 insertions(+), 7 deletions(-)

             reply	other threads:[~2023-07-23 20:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-23 20:06 Steven Rostedt [this message]
2023-07-23 20:06 ` [for-linus][PATCH 1/3] tracing: Remove unused extern declaration tracing_map_set_field_descr() Steven Rostedt
2023-07-23 20:06 ` [for-linus][PATCH 2/3] ring-buffer: Do not swap cpu_buffer during resize process Steven Rostedt
2023-07-23 20:06 ` [for-linus][PATCH 3/3] tracing/histograms: Return an error if we fail to add histogram to hist_vars list 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=20230723200623.034313147@goodmis.org \
    --to=rostedt@goodmis.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mhiramat@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.