On Thu, Oct 14, 2010 at 4:30 PM, Ben Greear <greearb@xxxxxxxxxxxxxxx> wrote: > On 10/14/2010 04:19 PM, Luis R. Rodriguez wrote: >> >> Ok please try this patch, it cures it for me. > > Well, it got a lot further than normal, but it still > hit the poison check after a few minutes. > > Current test case is my app loading 130 or so stations, each running > wpa_supplicant. ÂAll were created, and quite a few had associated > when the poison check hit. > > So, it definitely looks like a step in the right direction, but > not fully fixed yet. > > I'll do some more testing with this patch applied and using just my > perl script to make sure the problem is reproducible outside of my > application. Ok, whatever userspace does it should not corrupt to kernel, unless its poking /dev/mem Luis -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
