From: Greg KH <gregkh@linuxfoundation.org>
To: Ignat Korchagin <ignat@cloudflare.com>
Cc: stable@vger.kernel.org, jolsa@kernel.org,
kernel-team <kernel-team@cloudflare.com>
Subject: Re: Request to backport "bpf: Add missing BPF_LINK_TYPE invocations" to 6.6 kernel
Date: Wed, 1 May 2024 19:21:55 +0200 [thread overview]
Message-ID: <2024050126-stank-unbaked-3489@gregkh> (raw)
In-Reply-To: <CALrw=nG=+tWmUGgBe5Tyip+PJiMPR_7FWG=e1Ws6OP8mDhqPZw@mail.gmail.com>
On Wed, May 01, 2024 at 05:13:17PM +0100, Ignat Korchagin wrote:
> Hello,
>
> We recently saw a KASAN report on a 6.6.27 kernel similar to [1] and
> noticed that commit 117211aa739a ("bpf: Add missing BPF_LINK_TYPE
> invocations") was never backported to the 6.6 stable tree. Is there a
> reason? Can it be backported?
>
> [1]: https://lore.kernel.org/bpf/ZXptoKRSLspnk2ie@xpf.sh.intel.com/
>
Please submit a backported and tested version of this, and you should
cc: the developers/maintainers involved as well.
thanks,
greg k-h
prev parent reply other threads:[~2024-05-01 17:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-01 16:13 Request to backport "bpf: Add missing BPF_LINK_TYPE invocations" to 6.6 kernel Ignat Korchagin
2024-05-01 17:21 ` Greg KH [this message]
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=2024050126-stank-unbaked-3489@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=ignat@cloudflare.com \
--cc=jolsa@kernel.org \
--cc=kernel-team@cloudflare.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