Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: craig <craig@haquarter.de>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: tcp: enforce receive buffer memory limits by allowing the tcp window to shrink
Date: Sat, 14 Oct 2023 12:38:14 -0400	[thread overview]
Message-ID: <ZSrD9s8UPGFq1Wpu@sashalap> (raw)
In-Reply-To: <MzUupJN3oxWdw7O3tyFkgevmIelXS340Dl-1oKnkGG-e4G5sqRpblEfCpbKyAzk3x3SmccNR9egn4F5j-H7eiojEJW1HlrtBIfxhamuf7W4=@haquarter.de>

On Fri, Oct 13, 2023 at 09:02:54AM +0000, craig wrote:
>Hi,
>
>I hope I'm doing this correctly, as per https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html, Option 2. :)
>
>Subject of the patch: tcp: enforce receive buffer memory limits by allowing the tcp window to shrink
>Full details including reproducers, impact, tests are available here: https://blog.cloudflare.com/unbounded-memory-usage-by-tcp-for-receive-buffers-and-how-we-fixed-it/
>
>commit ID: b650d953cd391595e536153ce30b4aab385643ac
>
>Why I think it should be applied:
>- linux TCP sessions are allocating more memory than they should
>- the kernel drops incoming packets which it should not drop
>- large amounts of memory can be saved (see https://blog.cloudflare.com/unbounded-memory-usage-by-tcp-for-receive-buffers-and-how-we-fixed-it/#memory)
>
>What kernel versions you wish it to be applied to: 6.1.x (stable).
>Thank you! :)

Queued up, thanks.

-- 
Thanks,
Sasha

      reply	other threads:[~2023-10-14 16:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-13  9:02 tcp: enforce receive buffer memory limits by allowing the tcp window to shrink craig
2023-10-14 16:38 ` Sasha Levin [this message]

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=ZSrD9s8UPGFq1Wpu@sashalap \
    --to=sashal@kernel.org \
    --cc=craig@haquarter.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox