From: Jiayuan Chen <jiayuan.chen@linux.dev>
To: "Ahmed, Aaron" <aarnahmd@amazon.com>,
Kuniyuki Iwashima <kuniyu@google.com>,
"edumazet@google.com" <edumazet@google.com>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"ncardwell@google.com" <ncardwell@google.com>,
aws-binance-tam <aws-binance-tam@amazon.com>
Subject: Re: [BUG] net: tcp: SO_LINGER with l_linger=0 leaks memory when closing sockets with pending send data
Date: Mon, 10 Aug 2026 09:50:45 +0800 [thread overview]
Message-ID: <e70aca6d-2dc4-4b68-bd1f-c73e9631d870@linux.dev> (raw)
In-Reply-To: <0A7EC161-4EE6-42D4-A10B-7B4C609C7B32@amazon.com>
On 8/8/26 11:42 AM, Ahmed, Aaron wrote:
> Hi,
>
> Following up since it's been a while. I've tested on 6.18.39 (latest
> 6.18.y LTS) and the issue is still present.
>
> Baseline (55,542 connections, one client SIGSTOP'd):
> TCP: inuse 55542 orphan 0 tw 1 alloc 55543 mem 8236
You may be misreading "inuse", it counts sockets in the TCP hash tables,
not all sockets on the host
Sockets can still exist in host even inuse is zero.
prev parent reply other threads:[~2026-08-10 1:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-18 0:19 [BUG] net: tcp: SO_LINGER with l_linger=0 leaks memory when closing sockets with pending send data Ahmed, Aaron
2026-04-18 0:44 ` Kuniyuki Iwashima
2026-04-18 1:06 ` Kuniyuki Iwashima
2026-04-27 22:26 ` Ahmed, Aaron
2026-04-28 0:15 ` Kuniyuki Iwashima
2026-05-15 21:03 ` Ahmed, Aaron
2026-05-27 0:25 ` Ahmed, Aaron
2026-05-27 0:52 ` Kuniyuki Iwashima
2026-05-29 0:41 ` Ahmed, Aaron
2026-06-19 22:58 ` Ahmed, Aaron
2026-06-26 20:26 ` Ahmed, Aaron
2026-08-08 3:42 ` Ahmed, Aaron
2026-08-09 3:21 ` Kuniyuki Iwashima
2026-08-10 1:50 ` Jiayuan Chen [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=e70aca6d-2dc4-4b68-bd1f-c73e9631d870@linux.dev \
--to=jiayuan.chen@linux.dev \
--cc=aarnahmd@amazon.com \
--cc=aws-binance-tam@amazon.com \
--cc=edumazet@google.com \
--cc=kuniyu@google.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox