mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Martin Steigerwald <Martin@lichtvoll.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: bugs/regressions: report in LKML or in bugzilla?
Date: Tue, 7 Dec 2010 09:41:21 -0800	[thread overview]
Message-ID: <20101207094121.364745f9.randy.dunlap@oracle.com> (raw)
In-Reply-To: <201012071639.58884.Martin@lichtvoll.de>

On Tue, 7 Dec 2010 16:39:46 +0100 Martin Steigerwald wrote:

> Hi!
> 
> 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.

> 
> 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@vger.kernel.org)
Probably same for #27392.


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

---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

  parent reply	other threads:[~2010-12-07 17:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-07 15:39 Martin Steigerwald
2010-12-07 16:12 ` Eric Dumazet
2010-12-07 21:02   ` Ben Hutchings
2010-12-07 21:28     ` Martin Steigerwald
2010-12-07 21:11   ` Martin Steigerwald
2010-12-07 17:41 ` Randy Dunlap [this message]
2010-12-07 21:04   ` Martin Steigerwald
2010-12-08 10:00     ` Florian Mickler

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20101207094121.364745f9.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=Martin@lichtvoll.de \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®