From: Greg KH <gregkh@linuxfoundation.org>
To: Jordan Rife <jrife@google.com>
Cc: Daniel Borkmann <daniel@iogearbox.net>, netdev@vger.kernel.org
Subject: Re: Stable Backport: net: Avoid address overwrite in kernel_connect
Date: Thu, 31 Aug 2023 22:26:04 +0200 [thread overview]
Message-ID: <2023083113-unwed-chalice-c8d6@gregkh> (raw)
In-Reply-To: <CADKFtnRw=9F7Epa2T1N_2Zeu4sj+YySuvVb-PTOdfiAF9g4cPA@mail.gmail.com>
On Thu, Aug 31, 2023 at 01:09:04PM -0700, Jordan Rife wrote:
> 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.
5.7 is a very old kernel version, please use the documentation from the
latest kernel version.
You can use "latest" instead of "v5.7" there.
> I saw "option 2" in
> https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
> which reads
>
> > send an email to stable@vger.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?
What's wrong with option 2?
thanks,
greg k-h
next prev parent reply other threads:[~2023-08-31 20:26 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
2023-08-31 20:09 ` Jordan Rife
2023-08-31 20:26 ` Greg KH [this message]
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=2023083113-unwed-chalice-c8d6@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