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:	Mon, 5 May 2008 21:12:10 +0300
From:	Adrian Bunk <bunk@...nel.org>
To:	Stefan Richter <stefanr@...6.in-berlin.de>
Cc:	SL Baur <steve@...acs.org>, linux-kernel@...r.kernel.org
Subject: Re: How to reduce the number of open kernel bugs

On Sat, May 03, 2008 at 05:43:25PM +0200, Stefan Richter wrote:
>
> Adrian, what is it that you criticize?  Was it an impolite tone in the  
> maintainer's responses, or do you believe that the maintainer lied to  
> the reporter?
> 
> Or did the maintainer miss to do something which he would be able to and  
> had the resources to do?
>
> Or did the maintainer refuse to fulfill an obligation?
> 
> If it is one of the latter points, is it that the maintainer failed,  
> according to your observation, to explain in more detail why he closed  
> the bug early, in a way that a person without deep technical insight  
> into the problem domain can parse?  Or to ask for information which  
> would bring the bug forward?  Or to analyze the problem deeper on his  
> own?  Or use the bugzilla system in a more sophisticated way (reassign,  
> set status, change title... instead of closing the bug and requiring the  
> reporter to create a different bug entry)?
>...

The only thing that was really bad was the tone.

When anyone says "he could anyway not done anything about the bug" 
that's not true since he e.g. noted himself APIC errors in the report,
and could have reassigned the bug accordingly. Or noted it in the 
bug - when I touch a bug (as I did with this one before) I'm putting 
myself to the Cc, and I read what happens later in the bug.

But that's not the problem. The problem was the (repeated) closing of a 
bug in a way that expresses to a submitter that bug reports were 
unwanted.

> Stefan Richter

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ