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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Wed, 21 Dec 2022 12:30:07 +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 [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 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.
Powered by blists - more mailing lists