netdev - Re: Stable Backport: net: Avoid address overwrite in kernel

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CADKFtnRw=9F7Epa2T1N_2Zeu4sj+YySuvVb-PTOdfiAF9g4cPA@mail.gmail.com>
Date: Thu, 31 Aug 2023 13:09:04 -0700
From: Jordan Rife <jrife@...gle.com>
To: Greg KH <gregkh@...uxfoundation.org>
Cc: Daniel Borkmann <daniel@...earbox.net>, netdev@...r.kernel.org
Subject: Re: Stable Backport: net: Avoid address overwrite in kernel_connect

Greg,

Sorry if I've misunderstood. The netdev FAQ
(https://www.kernel.org/doc/html/v5.7/networking/netdev-FAQ.html#q-i-see-a-network-patch-and-i-think-it-should-be-backported-to-stable)
seemed to indicate that I should send network backport requests to
netdev. I saw "option 2" in
https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
which reads

> send an email to stable@...r.kernel.org containing the subject of the patch, the commit ID, why you think it should be applied, and what kernel version you wish it to be applied to.

Would "option 3" listed there be preferred?

-Jordan

On Thu, Aug 31, 2023 at 12:47 PM Greg KH <gregkh@...uxfoundation.org> wrote:
>
> 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>