On 5/14/19 8:44 AM, Joe Perches wrote:
On Tue, 2019-05-14 at 11:12 +0200, Johannes Berg wrote:
On Tue, 2019-05-14 at 17:10 +0800, Yibo Zhao wrote:
On 2019-05-14 17:05, Johannes Berg wrote:
On Tue, 2019-05-14 at 17: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.
[]
I was planning to use WARN_ON_ONCE() in the first place to replace
WARN_ON() then after some discussion, we think removing it could be
better. So the first patch was based on my first version which is sent
incorrectly. Please check again.
[]
I guess changing it to WARN_ON_ONCE() makes sense,
WARN_ON_RATELIMIT exists.
We know the WARN hits, we have the backtrace, and it is easy enough (in my setup
at least) to reproduce this. So, the WARN logic has done its job.
Having more of these spam the kernel doesn't add much benefit I think.
Anyone have any suggestions on how to fix the underlying issue?
Thanks,
Ben
--
Ben Greear <greearb@xxxxxxxxxxxxxxx>
Candela Technologies Inc http://www.candelatech.com
