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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

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

On Friday 02 May 2008 10:42:21 Parag Warudkar wrote:
> Adrian Bunk <bunk <at> kernel.org> writes:
> > Maintainer:
> >
> > Yeah, in any case. I cannot fix it, since it's not a bug in the fobar
> > code. Please reopen a new bug and CC the architecture or PCI maintainer
> > or whatever person related to the bus, chipset or CPU, if you think the
> > foobar device still works. If the foobar hardware got corrupted, you
> > already know what to do...
> >
> > I am well aware that loud flames are often the only working way of
> > communication in Linux kernel development, but we mustn't communicate
> > this way with bug submitters.
>
> Actually this way of _communication_ is better because the maintainer has -
>
> a) at least seen the bug
> b) made it clear upfront that he/she is not in a position to fix it and
> c) not inflicted a huge amount of follow up work for the reporter
> while giving no hope that it will be fixed.
>
> There is not much you can do if the maintainer feels he/she can't do
> anything - apart from fixing it yourself which has its limits.
> So the best that can be done is to communicate it clearly - that
> happens in this case.

With the above behavior, someone is reporting "I can use OS's A, B and C with 
no problems - the hardware works perfectly. When I try to use Linux X.Y.Z the 
driver faults and makes things unusable." and the maintainer is saying "The 
driver is fine. I didn't write code that has any bugs in it. The problem is 
your hardware is broken."

That kind of response is irresponsible and idiotic. If the hardware works 
perfectly in every other OS - and possibly even previous versions of Linux - 
then obviously the hardware isn't broken. This is what Adrian was pointing 
out and is exactly what shouldn't be happening.

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/