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/5] tracing: Minor fixes and clean ups
Date: Tue, 11 Jul 2023 10:06:52 -0400	[thread overview]
Message-ID: <20230711140652.217008556@goodmis.org> (raw)


Tracing fixes and clean ups:

- Fix some missing-prototype warnings

- Fix user events struct args (did not include size of struct)
  When creating a user event, the "struct" keyword is to denote
  that the size of the field will be passed in. But the parsing
  failed to handle this case.

- Fix sample code for direct trampolines.
  The sample code for direct trampolines attached to handle_mm_fault().
  But the prototype changed and the direct trampoline sample code
  was not updated. Direct trampolines needs to have the arguments correct
  otherwise it can fail or crash the system.

- Remove unused ftrace_regs_caller_ret() prototype.

  git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git
trace/core

Head SHA1: 46b77ea28faeed56f1d1b63f9049c40b9eb3cbf5


Arnd Bergmann (1):
      tracing: arm64: Avoid missing-prototype warnings

Beau Belgrave (1):
      tracing/user_events: Fix struct arg size match check

Florent Revest (2):
      samples: ftrace: Save required argument registers in sample trampolines
      arm64: ftrace: Add direct call trampoline samples support

YueHaibing (1):
      x86/ftrace: Remove unsued extern declaration ftrace_regs_caller_ret()

----
 arch/arm64/Kconfig                          |  2 ++
 arch/arm64/include/asm/ftrace.h             |  4 +++
 arch/arm64/include/asm/syscall.h            |  3 +++
 arch/arm64/kernel/syscall.c                 |  3 ---
 arch/x86/kernel/ftrace.c                    |  1 -
 include/linux/ftrace.h                      |  8 ++++++
 kernel/trace/fgraph.c                       |  1 +
 kernel/trace/ftrace_internal.h              |  5 ++--
 kernel/trace/trace_events_user.c            |  3 +++
 kernel/trace/trace_kprobe_selftest.c        |  3 +++
 samples/ftrace/ftrace-direct-modify.c       | 34 ++++++++++++++++++++++++
 samples/ftrace/ftrace-direct-multi-modify.c | 40 +++++++++++++++++++++++++++++
 samples/ftrace/ftrace-direct-multi.c        | 25 ++++++++++++++++++
 samples/ftrace/ftrace-direct-too.c          | 40 ++++++++++++++++++++++++-----
 samples/ftrace/ftrace-direct.c              | 24 +++++++++++++++++
 15 files changed, 184 insertions(+), 12 deletions(-)

             reply	other threads:[~2023-07-11 14:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-11 14:06 Steven Rostedt [this message]
2023-07-11 14:06 ` [for-linus][PATCH 1/5] samples: ftrace: Save required argument registers in sample trampolines Steven Rostedt
2023-07-11 14:06 ` [for-linus][PATCH 2/5] arm64: ftrace: Add direct call trampoline samples support Steven Rostedt
2023-07-11 14:06 ` [for-linus][PATCH 3/5] x86/ftrace: Remove unsued extern declaration ftrace_regs_caller_ret() Steven Rostedt
2023-07-11 14:06 ` [for-linus][PATCH 4/5] tracing: arm64: Avoid missing-prototype warnings Steven Rostedt
2023-07-11 14:06 ` [for-linus][PATCH 5/5] tracing/user_events: Fix struct arg size match check 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=20230711140652.217008556@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.