netdev - Re: [RFC] net: ipv4: optional early cleanup of half-closed TCP sockets

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAFWXMN0aRnrb185FgExki-TOwee0w7CAgVpjfu35R7WLDtm+SQ@mail.gmail.com>
Date: Thu, 29 Jan 2026 22:21:32 +0530
From: Gopal Malaviya <gopalmalaviya53@...il.com>
To: Kuniyuki Iwashima <kuniyu@...gle.com>
Cc: netdev@...r.kernel.org
Subject: Re: [RFC] net: ipv4: optional early cleanup of half-closed TCP sockets

Hi,

Thanks for the userspace example using ss --kill, that is a helpful
reference point.

Apart from userspace approaches, the motivation for raising this as
an RFC comes from scenarios where half-closed sockets are reused by
application-managed connection pools before any external userspace
action can detect or intervene. In those cases, polling- or
admin-driven mechanisms tend to be reactive and can race with reuse.

The question I am trying to explore is whether a narrowly scoped,
opt-in kernel policy tied directly to TCP state transitions
(particularly FIN_WAIT2) could be useful for workloads that need
deterministic cleanup without relying on external tooling.

Happy to adjust scope or direction based on feedback.

Thanks,
Gopal Malaviya