[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20080413121831.d89dd424.akpm@linux-foundation.org>
Date: Sun, 13 Apr 2008 12:18:31 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Willy Tarreau <w@....eu>
Cc: "Rafael J. Wysocki" <rjw@...k.pl>, Tilman Schmidt <tilman@...p.cc>,
Valdis.Kletnieks@...edu, Mark Lord <lkml@....ca>,
David Miller <davem@...emloft.net>, jesper.juhl@...il.com,
yoshfuji@...ux-ipv6.org, jeff@...zik.org,
linux-kernel@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: Reporting bugs and bisection (was: Re: 2.6.25-rc8: FTP transfer
errors)
On Sun, 13 Apr 2008 20:47:30 +0200 Willy Tarreau <w@....eu> wrote:
> One other thing which might get confusing/frustrating on the
> user side is that currently, Linux is the *only* product which requires
> the bug reporter to find the fault change
That's because many (probably most) Linux bugs are dependent upon the
hardware which they run on, and developers cannot reproduce the failure on
their hardware. Other software products don't have that problem.
That being said.. four or five years ago, developers would often work
closely with the reporter working out why the reporter's failure was
occurring. Several days of back-and-forth.
We dont' do that as much nowadays - there's a tendency to
a) throw the problem back at the reporter, often asking them to bisect.
If the reporter is running a distro kernel (eg: Fedora) then that's
quite hard, and often isn't a think they have knowledge to do. So
they'll just disappear. Or
b) just ignore the report altogether.
--
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