linux-kernel - Re: RFC: building a regression tracking bot for Linux kernel development

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: <23587f44-573e-b0b2-30aa-6d68cbbab9d2@leemhuis.info>
Date:   Fri, 23 Apr 2021 13:11:20 +0200
From:   Thorsten Leemhuis <linux@...mhuis.info>
To:     Takashi Iwai <tiwai@...e.de>
Cc:     Greg KH <gregkh@...uxfoundation.org>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        "Rafael J. Wysocki" <rafael@...nel.org>,
        regressions@...ts.linux.dev,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Konstantin Ryabitsev <konstantin@...uxfoundation.org>,
        Pablo Neira Ayuso <pablo@...filter.org>,
        ksummit@...ts.linux.dev, workflows@...r.kernel.org
Subject: Re: RFC: building a regression tracking bot for Linux kernel
 development



On 23.04.21 13:01, Takashi Iwai wrote:
> On Fri, 23 Apr 2021 12:49:25 +0200,
> Thorsten Leemhuis wrote:
>>
>> On 23.04.21 12:11, Greg KH wrote:
>>> On Thu, Apr 22, 2021 at 09:16:40AM +0200, Thorsten Leemhuis wrote:
>>>> That can't be all
>>>> -----------------
>>>>
>>>> Of course the world is more complicated than the simple example scenario
>>>> above, as the devil is always in the details. The three most obvious
>>>> problems the initial ideal scenario left aside:
>>>>
>>>> * The reporter doesn't specify the #regzb tag at all. Regzbot can't do
>>>> anything about it, it sadly won't have visionary power and a AI engine
>>>> any time soon. Some human (for a while that often will be me) thus needs
>>>> to reply with the tag with a proper reply-to to the report to make
>>>> regboz track it.
>>>
>>> Any specific format/tag we can use to help make this easier?  Or is that
>>> just something that you are going to do "by hand" to start with?
>>
>> For now making sure regressions@...ts.linux.dev is added to the CCed of
>> any replies to regression reports would be a really big help to already
>> establish it as central place where they are all visible. Then no human
>> or bot needs to monitor hundreds of mailing list to find them -- which
>> obviously is doomed to fail and was one of the pain points when I
>> tracked regressions manually years ago.
> 
> That sounds great.

Good :-D

> One thing I still wonder is how to populate the report from distro bug
> trackers.  AFAIK, many reports come from there directly or
> indirectly.
> 
> Can regzbot can have a reference to bug trackers or such?

There was a small, easily missed note about that in the long mail that
started this thread:

```
 * Initially it won't be possible to track reports that are filed in bug
trackers; but this use-case will be kept in mind during the design to
make sure such a functionality can be added later easily.
```

When I wrote that I mainly had the bug trackers used by the ACPI/PM and
DRM people in mind, but yes, making sure that it works for distro
tracker as well is a good point. Thx for bringing this to my attention.
And FWIW: I might leave that out initially, but I guess it won't take
too long before I will add this.

Ciao, Thorsten