linux-kernel - Thorsten is tracking regression again and could need a little help (was: Re: Linux 5.15)

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]

Message-ID: <a365ffb9-a4d2-b1d7-7cd7-dd9d7039e04e@leemhuis.info>
Date:   Mon, 1 Nov 2021 05:49:40 +0100
From:   Thorsten Leemhuis <regressions@...mhuis.info>
To:     Linus Torvalds <torvalds@...ux-foundation.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        "regressions@...ts.linux.dev" <regressions@...ts.linux.dev>
Subject: Thorsten is tracking regression again and could need a little help
 (was: Re: Linux 5.15)

On 31.10.21 22:09, Linus Torvalds wrote:
> It's been calm, and I have no excuse to add an extra rc, so here we
> are, with v5.15 pushed out, and the merge window starting tomorrow.

TLDR: Please tell me directly (by CC or forward) or via regzbot (see
below) about any regression reports you stumble upon, as I'm giving
regression tracking another shot. This time I'm doing it with the help
of a bot, which really could need a lot to chew on for a proper test-run.

Hi everyone! Years ago I did regression tracking for the Linux kernel
for a while. Back then tracking and writing weekly reports was a manual
and quite exhausting effort. Nevertheless, I'm giving regression
tracking another shot. But this time I'll leave the hard work to a bot I
wrote just for this purpose, which is specifically tailored to the needs
of Linux kernel development. I tested this 'regzbot' a little in the
past few weeks, but I need more regression reports now to shake out bugs
and see where things might need big adjustments or fine-tuning.

Hence, if you see any regression reports, please tell be about them, for
example by simply forwarding the mail to regressions@...mhuis.info or
CCing that address on a reply. I'll handle everything else then and tell
regzbot about it. But if you feel adventurous, you can also skip me as
the man-in-the-middle and tell the bot directly. To do that, just send a
reply to the report to the regressions mailing list
(regressions@...ts.linux.dev) either directly or by CCing it on a reply
you would have written anyway; when doing so, place something like
'#regzbot ^introduced v5.15..' (separated by blank lines) somewhere in
the text, as outlined in regzbot's 'getting started guide' or its
reference documentation:
https://gitlab.com/knurd42/regzbot/-/blob/main/docs/getting_started.md
https://gitlab.com/knurd42/regzbot/-/blob/main/docs/reference.md

That's it, regzbot then on its next run will add the report to the list
of tracked regression. I'll keep an eye on things and try to fix any
problems I notice, as there likely will be a few. But then doesn't need
to bother you.

There is one thing that would really help: if one or two subsystem
maintainers could give regzbot a shot for all the regression reports
they get, even for easy fixes, as the bot really needs something to chew
on. Any volunteers?

As years ago I'll send weekly regression reports, but this time they
will get generated directly from regzbot. But thx to the bot there is
now also a web-view which provides an always up2date view into the data
gathered by regzbot:
https://linux-regtracking.leemhuis.info/regzbot/mainline/

Ciao, Thorsten