Linux kernel -stable discussions
 help / color / mirror / Atom feed
* Request to backport "bpf: Add missing BPF_LINK_TYPE invocations" to 6.6 kernel
@ 2024-05-01 16:13 Ignat Korchagin
  2024-05-01 17:21 ` Greg KH
  0 siblings, 1 reply; 2+ messages in thread
From: Ignat Korchagin @ 2024-05-01 16:13 UTC (permalink / raw)
  To: stable, jolsa; +Cc: kernel-team

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/

Ignat

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Request to backport "bpf: Add missing BPF_LINK_TYPE invocations" to 6.6 kernel
  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
  0 siblings, 0 replies; 2+ messages in thread
From: Greg KH @ 2024-05-01 17:21 UTC (permalink / raw)
  To: Ignat Korchagin; +Cc: stable, jolsa, kernel-team

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2024-05-01 17:21 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox