From: Greg KH <gregkh@linuxfoundation.org>
To: Sherry Yang <sherry.yang@oracle.com>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
rostedt@goodmis.org, mingo@redhat.com
Subject: Re: [PATCH 5.4.y 0/2] tracing/kprobes: Backport request about
Date: Tue, 1 Oct 2024 10:11:56 +0200 [thread overview]
Message-ID: <2024100111-alone-fructose-1103@gregkh> (raw)
In-Reply-To: <20240927214359.7611-1-sherry.yang@oracle.com>
On Fri, Sep 27, 2024 at 02:43:57PM -0700, Sherry Yang wrote:
> 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
As per the documentation, we can't take patches for older kernels and
not newer ones, otherwise you will have regressions when you finally
move off this old kernel to a modern one :)
Please resend ALL of the needed backports, not just one specific kernel.
I'm dropping these from my review queue now.
thanks,
greg k-h
next prev parent reply other threads:[~2024-10-01 8:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-27 21:43 [PATCH 5.4.y 0/2] tracing/kprobes: Backport request about Sherry Yang
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 ` Greg KH [this message]
2024-10-11 16:55 ` [PATCH 5.4.y 0/2] tracing/kprobes: Backport request about 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=2024100111-alone-fructose-1103@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.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