linux-kernel - Re: How to reduce the number of open kernel 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] [day] [month] [year] [list]

Date:	Fri, 2 May 2008 19:15:37 -0400
From:	Daniel Hazelton <dhazelton@...er.net>
To:	Adrian Bunk <bunk@...nel.org>
Cc:	Parag Warudkar <parag.warudkar@...il.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: How to reduce the number of open kernel bugs

On Friday 02 May 2008 14:01:51 Adrian Bunk wrote:
> On Fri, May 02, 2008 at 01:30:23PM -0400, Parag Warudkar wrote:
> > On Fri, May 2, 2008 at 12:29 PM, Daniel Hazelton <dhazelton@...er.net>
> > wrote: This is what Adrian was pointing
<snip>
>
> From what I forwarded it's clear that we have a bug somewhere in the
> kernel.
>
> And the maintainer might well be right that it's not in his driver.

This is something that can't be known without enough information from the 
person reporting the bug. From what you posted of the bugzilla entry it's 
unclear whether the reporter did post more than his simple description or 
not.

However, the point is well made and I, at least, agree. (whatever that may be 
worth - I've never managed to finish a patch for anything without seeing the 
equivalent show up here later)

> Which means to reassign the bug to the maintainer of the area this bug
> is in.

Yep. Closing it with a comment of "broken hardware" is an incorrect response. 
Doubly or trebly so if the bugzilla entry didn't contain enough information 
to even determine whether the bug was in the driver or not.

DRH

-- 
Dialup is like pissing through a pipette. Slow and excruciatingly painful.
--
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/