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: Francis Laniel <flaniel@linux.microsoft.com>,
	linux-kernel@vger.kernel.org,
	Steven Rostedt <rostedt@goodmis.org>,
	Masami Hiramatsu <mhiramat@kernel.org>
Subject: [GIT PULL] probes: fixes for v6.6-rc6.2
Date: Sat, 21 Oct 2023 19:01:24 +0900	[thread overview]
Message-ID: <20231021190124.9e591c603d227379453d3307@kernel.org> (raw)

Hi Linus,

Probes fixes for v6.6-rc6.2:

- kprobe-events: Fix kprobe events to reject if the attached symbol
  is not unique name because it may not the function which the user
  want to attach to. (User can attach a probe to such symbol using
  the nearest unique symbol + offset.)

- selftest: Add a testcase to ensure the kprobe event rejects non
  unique symbol correctly.


Please pull the latest probes-fixes-v6.6-rc6.2 tree, which can be found at:


  git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git
probes-fixes-v6.6-rc6.2

Tag SHA1: d6e0322d9de05369d84aa0e8acc0c03978b50a40
Head SHA1: 03b80ff8023adae6780e491f66e932df8165e3a0


Francis Laniel (2):
      tracing/kprobes: Return EADDRNOTAVAIL when func matches several symbols
      selftests/ftrace: Add new test case which checks non unique symbol

----
 kernel/trace/trace_kprobe.c                        | 63 ++++++++++++++++++++++
 kernel/trace/trace_probe.h                         |  1 +
 .../ftrace/test.d/kprobe/kprobe_non_uniq_symbol.tc | 13 +++++
 3 files changed, 77 insertions(+)
 create mode 100644 tools/testing/selftests/ftrace/test.d/kprobe/kprobe_non_uniq_symbol.tc

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

             reply	other threads:[~2023-10-21 10:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-21 10:01 Masami Hiramatsu [this message]
2023-10-21 18:29 ` 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=20231021190124.9e591c603d227379453d3307@kernel.org \
    --to=mhiramat@kernel.org \
    --cc=flaniel@linux.microsoft.com \
    --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®