From: nramaswamy@openai.com
To: Jakub Kicinski <kuba@kernel.org>
Cc: Neil Ramaswamy <nramaswamy@openai.com>, netdev@vger.kernel.org
Subject: Re: [PATCH net 1/2] tcp: restore RACK list membership when undoing loss
Date: Thu, 1 Oct 2026 16:33:50 -0700 [thread overview]
Message-ID: <20261001233352.75988-2-nramaswamy@openai.com> (raw)
In-Reply-To: <20261001160720.0a663ec7@kernel.org>
From: Neil Ramaswamy <nramaswamy@openai.com>
On Thu, 1 Oct 2026 16:07:20 -0700, Jakub Kicinski wrote:
> Could you add to the commit msg if this was found with an LLM scan
> of the source code or its been seen in prod?
Yes, I can add that to the commit message once review settles. My investigation
started from seeing repeated TCP stalls in prod and the mitigation that seemed
to prevent these stalls was limiting SO_SNDBUF to 96 KiB. It also seems like
others have seen similar symptoms before [1] but I can't definitively say it's
the same root cause.
[1] https://lore.kernel.org/netdev/35A4DDAA-7E8D-43CB-A1F5-D1E46A4ED42E@gmail.com/
next prev parent reply other threads:[~2026-10-01 23:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-26 0:25 [PATCH net 0/2] tcp: preserve RACK tracking across partial undo nramaswamy
2026-09-26 0:25 ` [PATCH net 1/2] tcp: restore RACK list membership when undoing loss nramaswamy
2026-09-30 2:13 ` Jiayuan Chen
2026-10-01 0:30 ` Kuniyuki Iwashima
2026-10-01 23:07 ` Jakub Kicinski
2026-10-01 23:33 ` nramaswamy [this message]
2026-09-26 0:25 ` [PATCH net 2/2] selftests: net: packetdrill: test RACK after partial undo nramaswamy
2026-09-28 21:53 ` [PATCH net 0/2] tcp: preserve RACK tracking across " nramaswamy
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=20261001233352.75988-2-nramaswamy@openai.com \
--to=nramaswamy@openai.com \
--cc=kuba@kernel.org \
--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