KernelTriage

DRAFT
This page is a draft, don't depend on any information here yet.

Introduction

The Linux kernel is a large and complex software project, and thus gets a lot of bug reports in the Fedora bugzilla instance. This effort attempts to triage these bugs to allow Fedora kernel maintainers to focus on real bugs and issues.

Steps taken for new bugs

The following actions should be taken on each new bug:

• If the reporter is not running the most current kernel update, ask them to duplicate with the newest kernel version available.

• If the report has a kernel OOPs that shows that their kernel is "tainted", ask reporter to duplicate without the tainting module.

• Note to the reporter the Kernel common problems page.

• If this is a feature request, point reporter upstream (also CLOSED->WONTFIX?)

• If the bug contains a patch, add "PATCH" to the subject and ask them to submit upstream (CLOSE also?)

• Severity is set according to:

 ** Won't boot -> severe
 ** Some functionality lost -> high
 ** cosmetic/warnings -> low

• If this is a regression from a previous Fedora kernel, add a 'regression' keyword. NOTE what regression means. ;)

• If the bug is pertaining to a config option that should be enabled/disabled/made modular, add 'kernel_config' keyword.

• The arch of the bug should be noted. If it's a secondary Fedora arch, the secondary arch team should be added to CC and/or a keyword added.

• The High level subsystem the bug is involved in should be noted and a Keyword added for it, as well as possibly a CC to subsystem maintainers

 ** general storage
 ** lvm
 ** Radeon/ATI graphics
 ** Intel graphics
 ** NV graphics
 ** Other graphics
 ** General
 ** Packaging of the fedora kernel
 ** Networking
 ** USB/Firewire
 ** NFS
 ** KVM/Libvirt
 

• Finally, the "Triaged" Keyword should be added.