Re: [BUG] New Kernel Bugs

On Tue, 13 Nov 2007 22:33:58 +0100 Jörn Engel <joern@xxxxxxxxx> wrote:

On Tue, 13 November 2007 15:18:07 -0500, Mark Lord wrote:

I just find it weird that something can be known broken for several -rc*
kernels before I happen to install it, discover it's broken on my own
machine,
and then I track it down, fix it, and submit the patch, generally all
within a
couple of hours. Where the heck was the dude(ess) that broke it ?? AWOL.

And when I receive hostility from the "maintainers" of said code for fixing
their bugs, well.. that really motivates me to continue reporting new ones..

Given a decent bug report, I agree that having the bug not looked at is
shameful. But what can a developer do if a bug report effectively reads
"there is some bug somewhere in recent kernels"? How can I know that in
this particular case it is my bug that I introduced? It could just as
easily be 50 other people and none of them are eager to debug it unless
they suspect it to be their bug.

It's relatively common that a regression in subsystem A will manifest as a
failure in subsystem B, and the report initially lands on the desk of the
subsystem B developers.

But that's OK. The subsystem B people are the ones with the expertise to
be able to work out where the bug resides and to help the subsystem A
people understand what went wrong.

Alas, sometimes the B people will just roll eyes and do nothing because
they know the problem wasn't in their code. Sometimes.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Relevant Pages

  • Re: [BUG] New Kernel Bugs
    ... kernels before I happen to install it, discover it's broken on my own ... Given a decent bug report, I agree that having the bug not looked at is ... But what can a developer do if a bug report effectively reads ...
    (Linux-Kernel)
  • Re: OT: productivity and long computing delays
    ... suggest immersing yourself in the second project during 2-hour gaps. ... (i.e. implement a new subsystem involving writing a lot). ... means I make a few small edits, then end up having to rebuild, and ... take this huge delay before I can find the next bug, ...
    (comp.lang.python)
  • Re: SimEvents2.0 questions (Libraries & Subsystems)
    ... This has been identified as a bug in SimEvents v2.0. ... SimEvents v2.0 doesn't support non-scalar signal input to a Discrete ... Any signal inputs to Discrete Event Subsystem must ...
    (comp.soft-sys.matlab)
  • Re: Bugzilla permissions
    ... reluctant to make it a complete free for all and let any new user edit ... any bug. ... However, for anyone running a subsystem, or anyone else ...
    (Linux-Kernel)
  • RE: [PATCH] likely cleanup: revert unlikely in ll_back_merge_fn
    ... the io subsystem being profiled. ... If you have a not-so-busy ... you like don't do enough IO to trigger a lot of ... I'm glad we actually found something interesting (bug or not). ...
    (Linux-Kernel)