linux-kernel - Re: Introducing bugbot

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:   Wed, 12 Apr 2023 15:23:25 +0300
From:   Kalle Valo <kvalo@...nel.org>
To:     Thorsten Leemhuis <linux@...mhuis.info>
Cc:     Konstantin Ryabitsev <konstantin@...uxfoundation.org>,
        workflows@...r.kernel.org, aros@....com,
        linux-kernel@...r.kernel.org, regressions@...ts.linux.dev,
        tools@...ux.kernel.org
Subject: Re: Introducing bugbot

Thorsten Leemhuis <linux@...mhuis.info> writes:

> CCing Kalle (JFYI)
>
> On 03.04.23 23:45, Konstantin Ryabitsev wrote:
>> 
>> 2. Start mailing list threads from pre-triaged bugzilla bugs. This works the
>>    opposite way and creates mailing list threads based on bug reports filed in
>>    bugzilla. The useful things here are:
>> 
>>    - bugbot only gets triggered on open bugs in Linux/Kernel that have the
>>      "bugbot" flag set to "+", which allows pre-triaging a bug before bugbot
>>      sends it to the mailing list
>> [...]
>
> Are there any policies or best practices on how people should/are
> allowed to use this? From what I can see it seems one needs to change
> the Product/Component of the bug to start a thread. I wonder if a few
> maintainers that are active in bugzilla might be annoyed by this, as
> that might break their workflow.
>
> Which puts me in an awkward position when I see regressions reports in
> bugzilla and would like to create threads for them. Using bugbot would
> be better then the manual forwards I do now, like this one:
>
> https://lore.kernel.org/all/ed31b6fe-e73d-34af-445b-81c5c644d615@leemhuis.info/
>
> But here I decided to *not* use bugbot, as I know Kalle sometimes is
> active in bugzilla -- and thus might hate it, if I re-categorize the bug.

Yeah, for me moving ath11k bugs away from Drivers/network-wireless
component is not really helpful. And for ath11k I try to look at all
reported bugs in bugzilla anyway, though just slowly.

While at it, I have some things on my wishlist to make my use of
bugzilla.kernel.org easier:

* A new state named UNCONFIRMED and have it as the default state for
  reported bugs. This would help triaging bugs as some of the reports
  are not valid. In other words only valid bugs would have NEW state.
  IIRC the Mozilla project did this back in the day.

* Use P3 as the default priority for the new bugs. I try to keep ath11k
  bugs in priority order but new reported bugs having P1 always messes
  up the list always.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches