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: <CAAVpQUBLvvhPjbmGSnUk_Up10AowDEeY_bR=ecZFoSN5ef1Sfw@mail.gmail.com>
Date: Mon, 15 Sep 2025 22:50:38 -0700
From: Kuniyuki Iwashima <kuniyu@...gle.com>
To: Jakub Sitnicki <jakub@...udflare.com>
Cc: netdev@...r.kernel.org, "David S. Miller" <davem@...emloft.net>, 
	Eric Dumazet <edumazet@...gle.com>, Jakub Kicinski <kuba@...nel.org>, 
	Neal Cardwell <ncardwell@...gle.com>, Paolo Abeni <pabeni@...hat.com>, kernel-team@...udflare.com, 
	Lee Valentine <lvalentine@...udflare.com>
Subject: Re: [PATCH net-next v4 2/2] selftests/net: Test tcp port reuse after
 unbinding a socket

On Sat, Sep 13, 2025 at 3:09 AM Jakub Sitnicki <jakub@...udflare.com> wrote:
>
> Exercise the scenario described in detail in the cover letter:
>
>   1) socket A: connect() from ephemeral port X
>   2) socket B: explicitly bind() to port X
>   3) check that port X is now excluded from ephemeral ports
>   4) close socket B to release the port bind
>   5) socket C: connect() from ephemeral port X
>
> As well as a corner case to test that the connect-bind flag is cleared:
>
>   1) connect() from ephemeral port X
>   2) disconnect the socket with connect(AF_UNSPEC)
>   3) bind() it explicitly to port X
>   4) check that port X is now excluded from ephemeral ports
>
> Signed-off-by: Jakub Sitnicki <jakub@...udflare.com>

Reviewed-by: Kuniyuki Iwashima <kuniyu@...gle.com>

Thanks!

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ