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

Date:	Fri, 2 May 2008 10:42:21 -0400
From:	"Parag Warudkar" <parag.warudkar@...il.com>
To:	"Adrian Bunk" <bunk@...nel.org>
Cc:	LKML <linux-kernel@...r.kernel.org>
Subject: Re: How to reduce the number of open kernel bugs

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.

Compare the above to -

* Reporter reports a bug.

* People in position to fix it  have no care for it and they show it
(By not even looking at it).

* Significant amount of time passes with no activity.

* Reporter receives a automated mail (bonus insult) - New release is
available, please retest with new release and open a new bug if the
problem still exists.

* Bug is closed

* Bug still exists in next release - reporter knows only when he/she
gets a chance to upgrade to next release (not always easy/possible).

Parag
--
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/