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: Mon, 24 Nov 2008 14:33:14 +0800 From: Zhu Yi <yi.zhu@...el.com> To: Marcel Holtmann <holtmann@...ux.intel.com> Cc: "John W. Linville" <linville@...driver.com>, Tomas Winkler <tomasw@...il.com>, "davem@...emloft.net" <davem@...emloft.net>, "linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>, "netdev@...r.kernel.org" <netdev@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "sfr@...b.auug.org.au" <sfr@...b.auug.org.au> Subject: Re: pull request: wireless-2.6 2008-11-18 On Mon, 2008-11-24 at 11:50 +0800, Marcel Holtmann wrote: > http://www.intellinuxwireless.org/bugzilla/show_bug.cgi?id=1703 > > and just relying on Bugzilla is not gonna be good enough. The Linux > kernel development has always been done via mailing lists. And while > there is a kernel and other Bugzillas, the main authority is still the > mailing list. So if you wanna get massive feedback or have testing > patches for debugging, then these need to be posted to linux-wireless > and not "hidden" into a Bugzilla. This is generally true for bugs easy to debug with. But in this example, the first reporter opened this bug 4 months ago. People usually don't follow thread for such a long time. There are also some reporters never show up in this ML. > I do have a perfect environment in Vancouver that allows me to trigger > this behavior within a few minutes. So if you really wanna debug this, > then just send debug patches to the mailing list and I am happy to run > such kernels. Can you still reproduce this bug with Johannes' patch? Thanks, -yi -- 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