public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Francis Laniel <flaniel@linux.microsoft.com>
To: Greg KH <gregkh@linuxfoundation.org>,
	Sherry Yang <sherry.yang@oracle.com>
Cc: linux-stable <stable@vger.kernel.org>,
	"sashal@kernel.org" <sashal@kernel.org>,
	"jeyu@kernel.org" <jeyu@kernel.org>,
	"rostedt@goodmis.org" <rostedt@goodmis.org>,
	"mingo@redhat.com" <mingo@redhat.com>,
	"ast@kernel.org" <ast@kernel.org>,
	"jolsa@kernel.org" <jolsa@kernel.org>,
	"mhiramat@kernel.org" <mhiramat@kernel.org>
Subject: Re: [PATCH 5.10.y 0/4] Backport fix commit for kprobe_non_uniq_symbol.tc test failure
Date: Fri, 11 Oct 2024 13:30:28 +0200	[thread overview]
Message-ID: <2204888.irdbgypaU6@pwmachine> (raw)
In-Reply-To: <D36D144A-02BB-4F79-B992-00C2BF6FB8C9@oracle.com>

Hi!

Le jeudi 10 octobre 2024, 18:11:51 CEST Sherry Yang a écrit :
> > On Oct 9, 2024, at 6:36 AM, Greg KH <gregkh@linuxfoundation.org> wrote:
> > 
> > On Tue, Oct 08, 2024 at 03:29:44PM -0700, Sherry Yang wrote:
> > 
> >> 5.10.y backported the commit 
> >> 09bcf9254838 ("selftests/ftrace: Add new test case which checks non
> >> unique symbol")
 which added a new test case to check non-unique symbol.
> >> However, 5.10.y didn't backport the kernel commit
> >> b022f0c7e404 ("tracing/kprobes: Return EADDRNOTAVAIL when func matches
> >> several symbols")to support the functionality from kernel side. Backport
> >> it in this patch series.
 
> >> The first two patches are presiquisites. The 4th commit is a fix commit
> >> for the 3rd one.
> > 
> > 
> > Should we just revert the selftest test instead?  That seems simpler
> > instead of adding a new feature to this old and obsolete kernel tree,
> > right?
> 
> 
> Sorry about the confusion. If kprobe attaches a function which is not the
> user wants to attach to, I would say it’s a bug. The test case uncovers the
> bug, so it’s a fix.
 
> Sherry
> 
> 

Let me add a bit of context as I wrote the third patch of this set.

It all started with a problem I had when trying to trace symbol names 
corresponding to different functions [1].
The patch was accepted to upstream and I wanted to backport it to stables.
Sadly, the patch itself was relying on other patches which were not present in 
some stable kernels, which leaded to various problems while releasing the new 
stable kernels (once again: sorry about having caused troubles here) [2]...

The current series seems to hold all the patches for the third one to work, so 
I guess we can now have it merged to stable without problems.

Best regards.
---
[1]: https://lore.kernel.org/all/20231018130042.3430f000@gandalf.local.home/T/
[2]: https://lore.kernel.org/all/2024010402-commerce-variably-ef86@gregkh/



  reply	other threads:[~2024-10-11 11:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-08 22:29 [PATCH 5.10.y 0/4] Backport fix commit for kprobe_non_uniq_symbol.tc test failure Sherry Yang
2024-10-08 22:29 ` [PATCH 5.10.y 1/4] kallsyms: Make kallsyms_on_each_symbol generally available Sherry Yang
2024-10-08 22:29 ` [PATCH 5.10.y 2/4] kallsyms: Make module_kallsyms_on_each_symbol " Sherry Yang
2024-10-08 22:29 ` [PATCH 5.10.y 3/4] tracing/kprobes: Return EADDRNOTAVAIL when func matches several symbols Sherry Yang
2024-10-08 22:29 ` [PATCH 5.10.y 4/4] tracing/kprobes: Fix symbol counting logic by looking at modules as well Sherry Yang
2024-10-09 13:36 ` [PATCH 5.10.y 0/4] Backport fix commit for kprobe_non_uniq_symbol.tc test failure Greg KH
2024-10-09 14:44   ` Steven Rostedt
2024-10-09 16:21   ` Sasha Levin
2024-10-10 16:11   ` Sherry Yang
2024-10-11 11:30     ` Francis Laniel [this message]
2024-10-11 12:13       ` Sasha Levin

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=2204888.irdbgypaU6@pwmachine \
    --to=flaniel@linux.microsoft.com \
    --cc=ast@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jeyu@kernel.org \
    --cc=jolsa@kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=mingo@redhat.com \
    --cc=rostedt@goodmis.org \
    --cc=sashal@kernel.org \
    --cc=sherry.yang@oracle.com \
    --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