From: Greg KH <gregkh@linuxfoundation.org>
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: Jordan Rife <jrife@google.com>, netdev@vger.kernel.org
Subject: Re: Stable Backport: net: Avoid address overwrite in kernel_connect
Date: Thu, 31 Aug 2023 21:47:45 +0200 [thread overview]
Message-ID: <2023083123-musky-exterior-5fa5@gregkh> (raw)
In-Reply-To: <7702c74e-482f-cd89-1d12-fb6869bd53f2@iogearbox.net>
On Thu, Aug 31, 2023 at 09:26:31PM +0200, Daniel Borkmann wrote:
> [ Adding Greg to Cc ]
>
> On 8/31/23 8:47 PM, Jordan Rife wrote:
> > Upstream Commit ID: 0bdf399342c5acbd817c9098b6c7ed21f1974312
> > Patchwork Link:
> > https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=0bdf399342c5
> > Requested Kernel Versions: 4.19, 5.4, 5.10, 5.15, 6.1, 6.4, 6.5
> >
> > This patch addresses an incompatibility between eBPF connect4/connect6
> > programs and kernel space clients such as NFS. At present, the issue
> > this patch fixes is a blocker for users that want to combine NFS with
> > Cilium. The fix has been applied upstream but the same bug exists with
> > older kernels.
Jordan:
<formletter>
This is not the correct way to submit patches for inclusion in the
stable kernel tree. Please read:
https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
for how to do this properly.
</formletter>
next prev parent reply other threads:[~2023-08-31 19:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-31 18:47 Stable Backport: net: Avoid address overwrite in kernel_connect Jordan Rife
2023-08-31 19:26 ` Daniel Borkmann
2023-08-31 19:47 ` Greg KH [this message]
2023-08-31 20:09 ` Jordan Rife
2023-08-31 20:26 ` Greg KH
2023-08-31 20:34 ` Jordan Rife
2023-09-02 7:29 ` 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=2023083123-musky-exterior-5fa5@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=daniel@iogearbox.net \
--cc=jrife@google.com \
--cc=netdev@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