From: "Ahmed, Aaron" <aarnahmd@amazon.com>
To: Kuniyuki Iwashima <kuniyu@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>,
"edumazet@google.com" <edumazet@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: Fri, 29 May 2026 00:41:30 +0000 [thread overview]
Message-ID: <A2E89DBD-8DF5-44A0-A09B-ACDBDB7FB31D@amazon.com> (raw)
In-Reply-To: <CAAVpQUBtKBzq36Wz9p3MaHR=G10-NFBtQXgGW3S3QV5THW2iCg@mail.gmail.com>
Hi Kuniyuki,
On Mon, Apr 27, 2026 at 5:16 PM Kuniyuki Iwashima <kuniyu@google.com> wrote:
> Sorry, I didn't have time to look into it.
No worries, thanks for the response.
>
> Could you try reproducing the issue on the latest net-next.git
> and/or the latest LTS tree 6.18.y ?
>
> And if you can still repro, please update README.md accordingly
> and upload your .config file since I don't have access to Amazon Linux :)
Reproduced on latest 6.18.y LTS (6.18.33). Updated the README
and uploaded .config:
https://github.com/aahmed71/tcp-linger-memleak-reproducer
Thanks,
Aaron
next prev parent reply other threads:[~2026-05-29 0:41 UTC|newest]
Thread overview: 11+ 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 [this message]
2026-06-19 22:58 ` Ahmed, Aaron
2026-06-26 20:26 ` Ahmed, Aaron
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=A2E89DBD-8DF5-44A0-A09B-ACDBDB7FB31D@amazon.com \
--to=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