On Fri, 2019-05-10 at 15:01 +0800, Yibo Zhao wrote: > In multiple SSID cases, it takes time to prepare every AP interface > to be ready in initializing phase. If a sta already knows everything it > needs to join one of the APs and sends authentication to the AP which > is not fully prepared at this point of time, AP's channel context > could be NULL. As a result, warning message occurs.
Please share the dump, I don't think this should be happening. I think this warning did what it was supposed to, uncover a bug; rather than remove the warning we should fix the bug. > Even worse, if the AP is under attack via tools such as MDK3 and massive > authentication requests are received in a very short time, console will > be hung due to kernel warning messages. I don't buy this, it's just a WARN_ON_ONCE(). > If this case can be hit during normal functionality, there should be no > WARN_ON(). Those should be reserved to cases that are not supposed to be > hit at all or some other more specific cases like indicating obsolete > interface. I agree, but right now I'm inclined to think it's a bug elsewhere rather than normal operation. johannes _______________________________________________ ath10k mailing list [email protected] http://lists.infradead.org/mailman/listinfo/ath10k
