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

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]

Date:   Thu, 22 Dec 2022 13:20:00 +0100
From:   Thorsten Leemhuis <regressions@...mhuis.info>
To:     "regressions@...ts.linux.dev" <regressions@...ts.linux.dev>
Cc:     netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PULL] Networking for next-6.1 #forregzbot



On 21.12.22 12:30, Thorsten Leemhuis wrote:
> [Note: this mail contains only information for Linux kernel regression
> tracking. Mails like these contain '#forregzbot' in the subject to make
> then easy to spot and filter out. The author also tried to remove most
> or all individuals from the list of recipients to spare them the hassle.]
> 
> On 16.12.22 11:49, Jiri Slaby wrote:
>>
>> 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.
> 
> Thanks for the report. To be sure below issue doesn't fall through the
> cracks unnoticed, I'm adding it to regzbot, my Linux kernel regression
> tracking bot:
> 
> #regzbot ^introduced 28044fc1d495
> #regzbot title new: regression tests of python-ephemeral-port-reserve fail
> #regzbot ignore-activity

#regzbot monitor:
https://lore.kernel.org/all/20221221151258.25748-1-kuniyu@amazon.com/
#regzbot fix: tcp: Add TIME_WAIT sockets in bhash2

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)

P.S.: As the Linux kernel's regression tracker I deal with a lot of
reports and sometimes miss something important when writing mails like
this. If that's the case here, don't hesitate to tell me in a public
reply, it's in everyone's interest to set the public record straight.