linux-kernel - Re: RFC: Updating the LKML bug reporting/updating framework

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200910261412.07980.elendil@planet.nl>
Date:	Mon, 26 Oct 2009 14:12:05 +0100
From:	Frans Pop <elendil@...net.nl>
To:	Robert Bradbury <robert.bradbury@...il.com>
Cc:	tmb@...driva.org, linux-kernel@...r.kernel.org
Subject: Re: RFC: Updating the LKML bug reporting/updating framework

Robert Bradbury wrote:
> Given the bugzilla database, is the LKML with its high volume and
> noise level (IMO), now largely obsolete [1]?

No, it's not. Many issues benefit from a mail-based discussion where many 
people can follow the thread and jump in if something strikes them.
People subscribed to lkml will generally have their own methods of 
filtering out mails/subjects/threads that interest them.

Some subsystems (like acpi) prefer to handle bugs using bugzilla; others 
(netdev, ide) have dedicated mailing lists. All regressions are tracked in 
bugzilla, even if many are initially reported on mailing lists.

lkml still has an important function for those who wish to keep a good 
general overview of what's happening. There are a few people who keep an 
active watch on lkml to spot bug reports and to ensure they are brought to 
the attention of the right people.
You are not required to subscribe to lkml to report an issue on it: the 
policy is to always reply-to-all.

If you prefer to use bugzilla, go ahead. Some subsystem maintainers will 
then handle the bug in bugzilla; others may switch to email.

> (I think I a Google search may have led me in the direction that it was
> the place to report bugs).

It depends. It's the one place where you can always report an issue if you 
don't know where else to report it. The best way to report issues is to do 
so directly to relevant maintainers, but that requires some familiarity 
with the source and the community.

Cheers,
FJP
--
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/