linux-kernel - Re: [PULL] Networking for next-6.1

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 for Android: free password hash cracker in your pocket

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

Date:   Tue, 20 Dec 2022 07:22:56 +0100
From:   Jiri Slaby <jirislaby@...nel.org>
To:     Kuniyuki Iwashima <kuniyu@...zon.com>
Cc:     davem@...emloft.net, joannelkoong@...il.com, kuba@...nel.org,
        linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
        pabeni@...hat.com, edumazet@...gle.com
Subject: Re: [PULL] Networking for next-6.1

On 19. 12. 22, 0:25, Kuniyuki Iwashima wrote:
> From:   Jiri Slaby <jirislaby@...nel.org>
> Date:   Fri, 16 Dec 2022 11:49:01 +0100
>> Hi,
>>
>> On 04. 10. 22, 7:20, Jakub Kicinski wrote:
>>> Joanne Koong (7):
>>
>>>         net: Add a bhash2 table hashed by port and address
>>
>> This makes regression tests of python-ephemeral-port-reserve to fail.
>>
>> I'm not sure if the issue is in the commit or in the test.
> 
> Hi Jiri,
> 
> Thanks for reporting the issue.
> 
> It seems we forgot to add TIME_WAIT sockets into bhash2 in
> inet_twsk_hashdance(), therefore inet_bhash2_conflict() misses
> TIME_WAIT sockets when validating bind() requests if the address
> is not a wildcard one.
> 
> I'll fix it.

Hi,

is there a fix for this available somewhere yet?

thanks,
-- 
js
suse labs