> Guy, > > > We understand that these two issues need to be taken care of, and they > > will be. My concern is that if current patches won't be merged soon, > > we will have to pay the effort to rebase the patches again. We are > > very limited with resources dedicated to supporting the merge of > > 802.11n to wireless-dev. This mailing list taught us in the "hard way" > > in the recent months: submit often submit early... So for making Ron's > > work efficient I suggest to merge his patches and let him do the fixes > > on top of them, specially since the two fixes are not 802.11n core > > critical issues and don't break any existing working flows. Do you > > feel comfortable with this approach? > > I understand your concern, however, if for some reason this doesn't > happen quickly enough we'll end up with code that is vulnerable in weird > ways. I'd have no issue with these patches if deaggregation support was > optional until we have the patchset that reworks that code. Can we do > that? I would have to mention at this point that A-MSDU deaggregation is obligatory according to the 802.11n, so excluding it would be a spec violation. What I will do is to put some out-of-band effort here, fixing the rx_h_data infrastructure, so it will be able to support rx_h_amsdu as well, thus eliminating the EAPOL bug. I hope that this fix will be ready soon in order to enable the merge, and then i will move on to next steps. Ron > johannes > > - 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
