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] [thread-next>] [day] [month] [year] [list]
Message-ID: <2ef5d790-5068-41f5-881f-5d2f1e6315e3@redhat.com>
Date: Tue, 20 Aug 2024 13:04:30 +0200
From: Paolo Abeni <pabeni@...hat.com>
To: Jason Xing <kerneljasonxing@...il.com>, davem@...emloft.net,
 edumazet@...gle.com, kuba@...nel.org, dsahern@...nel.org,
 ncardwell@...gle.com, kuniyu@...zon.com
Cc: netdev@...r.kernel.org, Jason Xing <kernelxing@...cent.com>,
 Jade Dong <jadedong@...cent.com>
Subject: Re: [PATCH v2 net-next] tcp: avoid reusing FIN_WAIT2 when trying to
 find port in connect() process

On 8/15/24 13:37, Jason Xing wrote:
> From: Jason Xing <kernelxing@...cent.com>
> 
> We found that one close-wait socket was reset by the other side
> which is beyond our expectation, 

I'm unsure if you should instead reconsider your expectation: what if 
the client application does:

shutdown(fd, SHUT_WR)
close(fd); // with unread data

?

Thanks,

Paolo


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ