Re: bugs/regressions: report in LKML or in bugzilla?

[Martin Steigerwald]

Am Dienstag 07 Dezember 2010 schrieb Randy Dunlap:
> On Tue, 7 Dec 2010 16:39:46 +0100 Martin Steigerwald wrote:
[...]
> > I reported some regressions to bugzilla that did not receive any
> > attentation so far:
> > 
> > [Bug 23792] New: openvpn: failure to unregister tap1 device, possibly
> > related to some netconsole issue
> > https://bugzilla.kernel.org/show_bug.cgi?id=23792
> > 
> > [Bug 23642] New: easycap driver fails to compile in 2.6.37-rc3
> > https://bugzilla.kernel.org/show_bug.cgi?id=23642
> 
> That one has received attention.  I commented on it and I have posted
> a patch that fixes that particular build problem.

Sorry, I somehow missed that reply. Thanks.

> > A participant of a linux performance training I hold found a bug with
> > window scaling which did not receive any reply as well:
> > 
> > Bug 20312 -  System freeze with multiples of 32 in
> > /proc/sys/net/ipv4/tcp_adv_win_scale
> > https://bugzilla.kernel.org/show_bug.cgi?id=20312
> > 
> > 
> > Is it better to report on LKML? I have the impression that bug
> > reports onto the mailinglist are more easily recognized.
> 
> They are generally more visible and get more attention if they are
> posted on an appropriate mailing list.  #20312, e.g., should be posted
> on the netdev mailing list (netdev@xxxxxxxxxxxxxxx)
> Probably same for #27392.

Thanks for your hints.

> > I also find it difficult to find the right component when reporting a
> > problem in bugzilla. Thus reports might not go to the right persons.
> > 
> > Please advice.
> 
> Bugs that are posted to LKML usually are added to the kernel bugzilla
> by one of the bugzilla maintainers.  They would also select the
> component, so you could just try that route to see if it works better.

Or I create a Bugzilla to save bugzilla maintainers some work and post a 
hint on the mailinglist, too?

Ciao,
-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7

Attachment: signature.asc
Description: This is a digitally signed message part.