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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Mon, 24 Nov 2008 09:33:38 +0100
From:	Marcel Holtmann <>
To:	Zhu Yi <>
Cc:	"John W. Linville" <>,
	Tomas Winkler <>,
	"" <>,
	"" <>,
	"" <>,
	"" <>,
	"" <>
Subject: Re: pull request: wireless-2.6 2008-11-18

Hi Yi,

>> 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.

true to some degree, but searching mailing list archives is a lot  
simpler then bug reports.

>> 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?

we will see once I am back in Vancouver. Will be some time in December  



To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists