linux-kernel - Re: [PATCH v1 (RFC)] docs: discourage users from using bugzilla.kernel.org

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]

Message-ID: <6ca51584-1739-e532-d40e-e4447065ea1e@infradead.org>
Date:   Mon, 11 Jan 2021 10:14:07 -0800
From:   Randy Dunlap <rdunlap@...radead.org>
To:     Thorsten Leemhuis <linux@...mhuis.info>,
        Jonathan Corbet <corbet@....net>
Cc:     linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1 (RFC)] docs: discourage users from using
 bugzilla.kernel.org

On 1/10/21 4:10 AM, Thorsten Leemhuis wrote:
> * About 66 of those ~200 components will assign bugs to email addresses
>   that look valid, but 125 of them end with @kernel-bugs.osdl.org or
>   @kernel-bugs.kernel.org. Those domains do not exist anymore, mails
>   sent there bounce ('Unrouteable address'). It's possible that the
>   server might be rewriting those domain names and nevertheless
>   delivers new reports and comments by mails to some human; but it
>   seems more like they never get mailed to anyone and thus just linger
>   in the database; no wonder quite a few of bugs filed against such
>   components never get a single reply (see below).

Those @kernel-bugs email addresses should not be a problem:

  https://korg.docs.kernel.org/bugzilla.html#real-assignees-vs-virtual-assignees

AFAIK, USB bugs go to linux-usb@...r.kernel.org,
SCSI bugs go to linux-scsi@...r.kernel.org.

netdev didn't want bugs sent there automatically IIRC, so a
human takes care of doing that if warranted.

Andrew Morton takes MM bugs and Cc:s them to linux-mm mailing list
and then asks for discussion to continue on the mailing list.

We could/should probably see if we can add more project-specific
mailing lists to the automatic reporting -- but probably not LKML.

Otherwise some bug reports might never be heard about.

-- 
~Randy