From: Greg KH <gregkh@linuxfoundation.org>
To: Francis Laniel <flaniel@linux.microsoft.com>
Cc: stable@vger.kernel.org, Masami Hiramatsu <mhiramat@kernel.org>
Subject: Re: [PATCH 4.14.y 0/1] Return EADDRNOTAVAIL when func matches several symbols during kprobe creation
Date: Mon, 23 Oct 2023 12:23:36 +0200 [thread overview]
Message-ID: <2023102317-liberty-kelp-3492@gregkh> (raw)
In-Reply-To: <20231023094947.258663-1-flaniel@linux.microsoft.com>
On Mon, Oct 23, 2023 at 12:49:46PM +0300, Francis Laniel wrote:
> Hi.
>
>
> I received messages regarding problems to apply the upstream patch.
> I was able to reproduce the problem on the following stable kernels:
> * 4.14,
> * 4.19,
> * 5.4
> * and 5.10
> But it seems to be false positive for kernel 5.15 and 6.1, is this case possible
> or I did something wrong?
Did you try to build with the patch applied? That might be the issue
for those kernels.
thanks,
greg k-h
next prev parent reply other threads:[~2023-10-23 10:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-21 19:30 FAILED: patch "[PATCH] tracing/kprobes: Return EADDRNOTAVAIL when func matches" failed to apply to 4.14-stable tree gregkh
2023-10-23 9:49 ` [PATCH 4.14.y 0/1] Return EADDRNOTAVAIL when func matches several symbols during kprobe creation Francis Laniel
2023-10-23 9:49 ` [PATCH 4.14.y 1/1] tracing/kprobes: Return EADDRNOTAVAIL when func matches several symbols Francis Laniel
2023-10-23 10:23 ` Greg KH [this message]
2023-10-23 12:25 ` [PATCH 4.14.y 0/1] Return EADDRNOTAVAIL when func matches several symbols during kprobe creation Francis Laniel
2023-11-27 16:50 ` [PATCH 4.14.y] tracing/kprobes: Return EADDRNOTAVAIL when func matches several symbols Francis Laniel
2023-11-30 13:39 ` Greg KH
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=2023102317-liberty-kelp-3492@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=flaniel@linux.microsoft.com \
--cc=mhiramat@kernel.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