linux-kernel - Re: Reporting driver bugs.

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: <20060926181557.16a19343.akpm@osdl.org>
Date:	Tue, 26 Sep 2006 18:15:57 -0700
From:	Andrew Morton <akpm@...l.org>
To:	Jeff Garzik <jeff@...zik.org>
Cc:	Nigel Cunningham <ncunningham@...uxmail.org>,
	suspend2-devel <suspend2-devel@...ts.suspend2.net>,
	suspend2-users <suspend2-users@...ts.suspend2.net>,
	"Rafael J. Wysocki" <rjw@...k.pl>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: Reporting driver bugs.

On Tue, 26 Sep 2006 20:45:05 -0400
Jeff Garzik <jeff@...zik.org> wrote:

> Nigel Cunningham wrote:
> > Hi everyone.
> > 
> > I've been involved in a little discussion this morning about reporting
> > driver bugs. In the past, I've tended to point people directly to the
> > driver author, but I've learnt that the preferred thing is to get people
> > to open reports on bugzilla.kernel.org.
> > 
> > I'm therefore writing to ask if those of you who help with triage could
> > point people there as well.
> 
> Unfortunately there is no one right answer.  Some driver maintainers 
> don't see the bugzilla.kernel.org entry at all; others find it useful 
> for tracking purposes.
> 
> At the very least, one should make sure the driver author is always CC'd 
> on initial bug reports.
> 

I screen all bugzilla reports and ensure that each one gets to the appropriate developer, if there is one.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/