All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Wille Padnos <stephen.willepadnos@verizon.net>
To: John Bradford <john@grabjohn.com>
Cc: "Randy.Dunlap" <rddunlap@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: Dedicated kernel bug database
Date: Thu, 19 Dec 2002 17:23:03 -0500	[thread overview]
Message-ID: <3E0246C7.3010503@verizon.net> (raw)
In-Reply-To: <200212192155.gBJLtV6k003254@darkstar.example.net>

Hmmm.

It seems to me that a kernel bug tracking system has to have a pretty 
good knowledge (database) of  the kernel(s) it is meant to track. 
 Essentially, a user who has a problem can usually identify what the 
problem is ("my external firewire HD doesn't work"), but not where the 
cause may be (interrupts / filesystem drivers / mount tools / scsi 
generic / sbp2 / ieee1394 / pci / ACPI / APIC / VM / ...).

So, if a user could enter some keywords for their problem and get a list 
of possible subsystems that it depends on (along with maintainers for 
those subsystems), we'd be getting somewhere.

For the usb / apic / acpi / rtl8139 problem, I would enter something 
like USB keyboard, 8139too, local APIC, IO-APIC, VIA kt333, kernel 2.5.45-51

The wizardly database (knowing what each "leaf device" depends on), then 
finds the intersection of  subsystems that affect all (or some specified 
percentage) of the things the keywords match.

This requires a tree of dependencies (pretty much there - look at what 
headers are included in each source file) for each driver.

Of course, there are things that everything depends on (VM), which would 
probably want to be left out unless no higher level common ancestor of 
the problems can be found.

The trouble with searching a flat bug database is that you have to know 
what you're looking for.  If the bug tracker actually helped figure out 
the problem (where possible, of course), that would be a boon.

John Bradford wrote:

[snip snip]

>>| Overall, though, would you rather be presented with a list of
>>| categories, or a list of people and what parts of the code they
>>| maintain.  Personally, I think that a list of people is more
>>| intuitive, rather than an abstract list of categories, but I could be
>>| wrong.
>>
>>Do we have anyone targeted for interrupt routing problems (PIC, IO APIC,
>>ACPI, etc.)?
>>    
>>
>
>No.  I nominate Alan :-).
>
Agreed.  (can he be elected without knowing he's on the ballot? :)



  parent reply	other threads:[~2002-12-19 22:20 UTC|newest]

Thread overview: 74+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-19 13:35 Dedicated kernel bug database John Bradford
2002-12-19 17:33 ` Brian Jackson
2002-12-20  3:26   ` Martin J. Bligh
2002-12-19 17:48 ` Eli Carter
2002-12-19 18:49   ` Dave Jones
2002-12-19 19:49     ` Eli Carter
2002-12-19 20:12       ` John Bradford
2002-12-19 20:24         ` Eli Carter
2002-12-19 20:45           ` John Bradford
2002-12-19 19:52     ` John Bradford
2002-12-19 20:18       ` Dave Jones
2002-12-19 20:32         ` Randy.Dunlap
2002-12-19 20:42         ` John Bradford
2002-12-20  3:40           ` Martin J. Bligh
2002-12-20  9:48             ` John Bradford
2002-12-20 10:40               ` Dave Jones
2002-12-20 16:08               ` Martin J. Bligh
2002-12-20  3:35     ` Martin J. Bligh
2002-12-20 17:32       ` Jon Tollefson
2002-12-19 20:09 ` Bill Davidsen
2002-12-19 20:32   ` John Bradford
2002-12-19 21:11     ` Stephen Wille Padnos
2002-12-19 21:40       ` John Bradford
2002-12-19 21:32         ` Randy.Dunlap
2002-12-19 21:55           ` John Bradford
2002-12-19 21:57             ` Eli Carter
2002-12-19 21:55               ` Randy.Dunlap
2002-12-19 22:45               ` Hanna Linder
2002-12-20  1:39                 ` Martin J. Bligh
2002-12-20  2:01                   ` Hanna Linder
2002-12-20  2:20                     ` Martin J. Bligh
2002-12-20 15:09                       ` Jon Tollefson
2002-12-20 23:52                         ` Hanna Linder
2002-12-21  3:30                           ` Jon Tollefson
2002-12-20 10:35                     ` Dave Jones
2002-12-20 19:37                       ` Hanna Linder
2002-12-20  2:10                   ` Hanna Linder
2002-12-20  2:22                     ` Martin J. Bligh
2002-12-20  2:58                       ` Randy.Dunlap
2002-12-20  3:21                         ` Martin J. Bligh
     [not found]                   ` <31080000.1040418947@w-hlinder>
2002-12-20 21:43                     ` Dedicated kernel bug database + documentaion Hanna Linder
2002-12-20 21:59                       ` Randy.Dunlap
2002-12-20 22:01                         ` Martin J. Bligh
2002-12-20 21:59                       ` Eli Carter
2002-12-21  2:52                     ` Dedicated kernel bug database Martin J. Bligh
2002-12-21  3:27                       ` Jon Tollefson
2002-12-30 21:58                         ` Hanna Linder
     [not found]               ` <mailman.1040338801.24520.linux-kernel2news@redhat.com>
2002-12-19 23:59                 ` Pete Zaitcev
2002-12-20  0:19                   ` Hanna Linder
2002-12-20  0:24                     ` Pete Zaitcev
2002-12-20  1:01                       ` Hanna Linder
2002-12-20 10:32                         ` Dave Jones
2002-12-20 10:41                           ` Russell King
2002-12-20 10:30                     ` Dave Jones
2002-12-20 15:43                       ` Eli Carter
2002-12-19 22:23             ` Stephen Wille Padnos [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-12-19 17:46 Dan Kegel
2002-12-19 18:00 ` John Bradford
2002-12-19 18:08   ` Eli Carter
2002-12-19 20:08     ` John Bradford
2002-12-19 20:38       ` Eli Carter
2002-12-19 20:59         ` John Bradford
2002-12-19 21:14           ` Eli Carter
2002-12-20 14:23           ` Horst von Brand
2002-12-19 22:05         ` Dan Kegel
2002-12-19 22:26         ` Dan Kegel
2002-12-19 23:09           ` John Bradford
     [not found] <2CC936747EA1284DA378A18D730697420158A50E@exchacad.ms.gettysburg.edu>
2002-12-19 20:33 ` Justin Pryzby
2002-12-19 21:04 Heater, Daniel (IndSys, GEFanuc, VMIC)
2002-12-20  2:26 Dan Kegel
2002-12-20 11:18 Nicolas Mailhot
2002-12-22  2:50 Hell.Surfers
2002-12-22  9:16 ` John Bradford
2002-12-22 18:53 Adam J. Richter

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=3E0246C7.3010503@verizon.net \
    --to=stephen.willepadnos@verizon.net \
    --cc=john@grabjohn.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rddunlap@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.