linux-kernel - Re: Reporting Kernel Bugs

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]

Date:	Fri, 14 Oct 2011 13:23:57 -0700 (PDT)
From:	David Rientjes <rientjes@...gle.com>
To:	Jan Steinke <jan.steinke@...il.com>
cc:	linux-kernel@...r.kernel.org
Subject: Re: Reporting Kernel Bugs

On Fri, 14 Oct 2011, Jan Steinke wrote:

> > Just send an e-mail to appropriate mailinglist and CC 
> > responsible maintainer(s).
> > 
> > That's what many people prefer to bugzilla anyway.
> > 
> 
> How do I know the responsible maintainer(s)? How do I know if the bug is 
> confirmed or accepted?
> 

If you can figure out what subsystem is the likely source of the issue, 
then you can check the MAINTAINERS file for the appropriate people and 
mailing list.  If there's a panic or oops, find the source file that is to 
blame and use ./scripts/get_maintainer.pl -f <file>.  Otherwise, just 
report some unknown, untriaged error directly to 
linux-kernel@...r.kernel.org and be sure to cc Andrew Morton 
<akpm@...ux-foundation.org> who used to go through the kernel.org bugzilla 
quite often and send bug reports in the right direction.
--
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/