linux-kernel - How to improve PCI bug tracking?

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-next>] [day] [month] [year] [list]

Message-ID: <20170118225332.GA22960@bhelgaas-glaptop.roam.corp.google.com>
Date:   Wed, 18 Jan 2017 16:53:32 -0600
From:   Bjorn Helgaas <helgaas@...nel.org>
To:     linux-pci@...r.kernel.org
Cc:     linux-kernel@...r.kernel.org
Subject: How to improve PCI bug tracking?

I want to improve PCI bug tracking.  It feels like our bugs don't get
the attention they need, and I'm soliciting ideas for how to improve
this.

Current situation:

  - People often report bugs via email to linux-pci.  I think this
    is good because everybody can see it.

  - Even after an email report, I often request a bugzilla because
    (1) it helps keep things from being forgotten, (2) it's a
    convenient place to store bulky data, and (3) I like to have a
    bugzilla URL to include in the changelog of a patch that fixes the
    bug.

  - Sometimes people open a bugzilla directly.  I get email about
    these (along with one or two other people), but this is sort of a
    problem because linux-pci never sees it, sometimes I miss it, and
    things tend to languish.

  - Discussion on a bugzilla is only seen by people listed in the
    bugzilla, not on linux-pci.

I'm contemplating changing this so the bugzilla mail would also go to
linux-pci.

Any objections or alternate suggestions?

Bjorn