| 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
| ||
|
Date: Sat, 15 Oct 2011 14:01:19 +0200 From: Maciej Rutecki <maciej.rutecki@...il.com> To: David Rientjes <rientjes@...gle.com> Cc: Jan Steinke <jan.steinke@...il.com>, linux-kernel@...r.kernel.org Subject: Re: Reporting Kernel Bugs On piątek, 14 października 2011 o 22:23:57 David Rientjes wrote: > 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. For regression add my address to CC. When bugzilla comes back, then I create bug entry for regression. Regards -- Maciej Rutecki http://www.mrutecki.pl -- 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/
Powered by blists - more mailing lists