[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <D99F1DB5-4DDE-478A-BCB6-C510CAFC1C67@oracle.com>
Date: Fri, 11 Oct 2024 16:55:15 +0000
From: Sherry Yang <sherry.yang@...cle.com>
To: Greg KH <gregkh@...uxfoundation.org>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
linux-stable <stable@...r.kernel.org>,
"rostedt@...dmis.org"
<rostedt@...dmis.org>,
"mingo@...hat.com" <mingo@...hat.com>,
"sashal@...nel.org" <sashal@...nel.org>
Subject: Re: [PATCH 5.4.y 0/2] tracing/kprobes: Backport request about
Hi Greg,
> On Oct 1, 2024, at 1:11 AM, Greg KH <gregkh@...uxfoundation.org> wrote:
>
> 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.
I have sent the backports to 5.10.y, and Sasha queued them up. Can we get this series in your 5.4.y review queue again?
Sherry
Powered by blists - more mailing lists