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: <p73d51n1fup.fsf@bingen.suse.de>
Date:	29 Apr 2007 15:15:42 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Adrian Bunk <bunk@...sta.de>, Diego Calleja <diegocg@...il.com>,
	Chuck Ebbert <cebbert@...hat.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Linux 2.6.21

Linus Torvalds <torvalds@...ux-foundation.org> writes:

> On Sun, 29 Apr 2007, Adrian Bunk wrote:
> > 
> > That's exactly where Linus' "drop any bug reports that are more than a 
> > week old" suggestion is completely flawed - no matter what the submitter 
> > does, how often he tests latest kernels, noone will help him.
> 
> You talk, but what do you actually *suggest*?
> 
> Talk is cheap. You use to do the walk too, but you've already said that 
> you're not interested in that any more. So excuse me if I'm not impressed. 
> 
> The thing is, bugzilla is totally broken because it's designed to help 
> track bugs, but it's *not* designed to actually handle the much harder 
> problem, which is to actually get the *right* developers to be aware of 
> the *right* bugs!

This means we need people who figure out who to assign bugs too.
Aka bugmasters.

In theory it could be nearly automated. Figure out what files related
to the bug and assign to the last 5 people who submitted patches
for them and/or signed off. 

Ok I suppose it's not that easy -- you would need some human judgement.

BTW one big problem in our current bugzilla is that a lot of people
cannot reassign bugs they don't own. I sometimes see bugs that I don't
own bug I know who is responsible, but bugzilla doesn't allow me to do it.

So I think what would help:

- Ask more people to just categorize and reassign bugs (anybody interested?)
- Give more people in bugzilla the power to reassign arbitary bugs
(bugzilla maintainers would need to do that)

-Andi

-
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