mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Masami Hiramatsu (Google) <mhiramat@kernel.org>
Subject: [GIT PULL] probes: Fixes for 6.5-rc3
Date: Mon, 31 Jul 2023 00:06:21 +0900	[thread overview]
Message-ID: <20230731000621.1d34c8638a1285901fb6f9a7@kernel.org> (raw)

Hi Linus,

Probe fixes for 6.5-rc3:

- probe-events: Fix to add NULL check for some BTF API calls which can
  return error code and NULL.

- ftrace selftests: Fix to check fprobe and kprobe event correctly. This
  fixes a miss condition of the test command.

- kprobes: Prohibit probing on the function which starts from "__cfi_"
  and "__pfx_" since those are auto generated for kernel CFI and not
  executed.


Please pull the latest probes-fixes-v6.5-rc3 tree, which can be found at:


  git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git
probes-fixes-v6.5-rc3

Tag SHA1: 1586c2c77c542c0f9a20bfe5bbebfc739f8dbd2a
Head SHA1: de02f2ac5d8cfb311f44f2bf144cc20002f1fbbd


Masami Hiramatsu (Google) (3):
      tracing/probes: Fix to add NULL check for BTF APIs
      selftests/ftrace: Fix to check fprobe event eneblement
      kprobes: Prohibit probing on CFI preamble symbol

----
 kernel/kprobes.c                                           | 14 +++++++++++++-
 kernel/trace/trace_probe.c                                 |  8 ++++----
 .../selftests/ftrace/test.d/dynevent/add_remove_btfarg.tc  |  2 +-
 3 files changed, 18 insertions(+), 6 deletions(-)

-- 
Masami Hiramatsu (Google) <mhiramat@kernel.org>

             reply	other threads:[~2023-07-30 15:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-30 15:06 Masami Hiramatsu [this message]
2023-07-30 19:43 ` pr-tracker-bot

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=20230731000621.1d34c8638a1285901fb6f9a7@kernel.org \
    --to=mhiramat@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --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

all inboxes | Powered by JetHome®