Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Sherry Yang <sherry.yang@oracle.com>
To: linux-kernel@vger.kernel.org, stable@vger.kernel.org
Cc: rostedt@goodmis.org, mingo@redhat.com,
	gregkh@linuxfoundation.org, sherry.yang@oracle.com
Subject: [PATCH 5.4.y 0/2] tracing/kprobes: Backport request about
Date: Fri, 27 Sep 2024 14:43:57 -0700	[thread overview]
Message-ID: <20240927214359.7611-1-sherry.yang@oracle.com> (raw)

The new test case which checks non unique symbol kprobe_non_uniq_symbol.tc 
failed because of missing kernel functionality support from commit 
b022f0c7e404 ("tracing/kprobes: Return EADDRNOTAVAIL when func matches several symbols"). 
Backport it and its fix commit to 5.4.y together. Resolved minor context change conflicts.

Andrii Nakryiko (1):
  tracing/kprobes: Fix symbol counting logic by looking at modules as
    well

Francis Laniel (1):
  tracing/kprobes: Return EADDRNOTAVAIL when func matches several
    symbols

 kernel/trace/trace_kprobe.c | 76 +++++++++++++++++++++++++++++++++++++
 kernel/trace/trace_probe.h  |  1 +
 2 files changed, 77 insertions(+)

-- 
2.46.0


             reply	other threads:[~2024-09-27 21:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-27 21:43 Sherry Yang [this message]
2024-09-27 21:43 ` [PATCH 5.4.y 1/2] tracing/kprobes: Return EADDRNOTAVAIL when func matches several symbols Sherry Yang
2024-09-27 21:43 ` [PATCH 5.4.y 2/2] tracing/kprobes: Fix symbol counting logic by looking at modules as well Sherry Yang
2024-10-01  8:11 ` [PATCH 5.4.y 0/2] tracing/kprobes: Backport request about Greg KH
2024-10-11 16:55   ` Sherry Yang
2024-10-14  8:36     ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2024-10-14 16:06 Sherry Yang

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=20240927214359.7611-1-sherry.yang@oracle.com \
    --to=sherry.yang@oracle.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rostedt@goodmis.org \
    --cc=stable@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox