From: "Holger Hoffstätte" <holger@applied-asynchrony.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
Jakub Kicinski <kuba@kernel.org>,
Eric Dumazet <edumazet@google.com>
Subject: Re: Please queue up f4dca95fc0f6 for 6.9 et.al.
Date: Tue, 4 Jun 2024 18:26:02 +0200 [thread overview]
Message-ID: <ba29a0e9-8f4c-e209-fb2d-1ef80f97da6d@applied-asynchrony.com> (raw)
In-Reply-To: <2024060452-headrest-deny-2a5b@gregkh>
On 2024-06-04 17:44, Greg KH wrote:
> On Tue, Jun 04, 2024 at 04:56:24PM +0200, Holger Hoffstätte wrote:
>>
>> Just ${Subject} since it's a fix for a potential security footgun/DOS, whereever
>> commit 378979e94e95 ("tcp: remove 64 KByte limit for initial tp->rcv_wnd value")
>> has been queued up.
>
> Only applies to 6.9.y, have backports for older kernels?
No, sorry - I'm just the messenger here and moved everything to 6.9 already.
Cc'ing Jakub and Eric.
My understanding is that the previous commit was a performance enhancement,
so if this turns out to be too difficult then maybe 378979e94e95 ("tcp: remove
64 KByte limit for initial tp->rcv_wnd value") should just not be merged either.
I have both patches on 6.9 but really cannot say whether they should go to
older releases.
Let's wait for Jakub or Eric.
cheers
Holger
next prev parent reply other threads:[~2024-06-04 16:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-04 14:56 Please queue up f4dca95fc0f6 for 6.9 et.al Holger Hoffstätte
2024-06-04 15:44 ` Greg KH
2024-06-04 16:26 ` Holger Hoffstätte [this message]
2024-06-04 16:32 ` Eric Dumazet
2024-06-04 16:35 ` Eric Dumazet
2024-06-04 18:03 ` Holger Hoffstätte
2024-06-04 16:47 ` Holger Hoffstätte
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=ba29a0e9-8f4c-e209-fb2d-1ef80f97da6d@applied-asynchrony.com \
--to=holger@applied-asynchrony.com \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=kuba@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.