From: Yibo Zhao <yiboz@codeaurora.org>
To: Ben Greear <greearb@candelatech.com>
Cc: Zhi Chen <zhichen@codeaurora.org>,
linux-wireless@vger.kernel.org, ath10k@lists.infradead.org
Subject: Re: [PATCH] mac80211: remove warning message
Date: Mon, 13 May 2019 14:20:26 +0800 [thread overview]
Message-ID: <0247de90c551b76aed1f9647f9b274c0@codeaurora.org> (raw)
In-Reply-To: <7119f24f-5b88-629a-d507-73776b841f65@candelatech.com>
On 2019-05-10 22:04, Ben Greear wrote:
> On 05/10/2019 12:01 AM, 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.
>>
>> 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.
>
> Since it is a WARN_ON_ONCE, how it the console hang due to warnings?
> You should
> get no more than once per boot?
>
Hi Ben,
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 patch was based on my first version. Sorry for the
confusing. Will raise another one.
> I have no problem with removing it though. Seems a harmless splat and
> I removed
> it from my tree some time back as well.
>
> Thanks,
> Ben
>
>>
>> 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.
>>
>> Signed-off-by: Zhi Chen <zhichen@codeaurora.org>
>> Signed-off-by: Yibo Zhao <yiboz@codeaurora.org>
>> ---
>> net/mac80211/ieee80211_i.h | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/net/mac80211/ieee80211_i.h b/net/mac80211/ieee80211_i.h
>> index 2ae0364..f39c289 100644
>> --- a/net/mac80211/ieee80211_i.h
>> +++ b/net/mac80211/ieee80211_i.h
>> @@ -1435,7 +1435,7 @@ struct ieee80211_local {
>> rcu_read_lock();
>> chanctx_conf = rcu_dereference(sdata->vif.chanctx_conf);
>>
>> - if (WARN_ON_ONCE(!chanctx_conf)) {
>> + if (!chanctx_conf) {
>> rcu_read_unlock();
>> return NULL;
>> }
>>
--
Yibo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2019-05-13 6:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-10 7:01 [PATCH] mac80211: remove warning message Yibo Zhao
2019-05-10 14:04 ` Ben Greear
2019-05-13 6:20 ` Yibo Zhao [this message]
2019-05-14 8:44 ` Johannes Berg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0247de90c551b76aed1f9647f9b274c0@codeaurora.org \
--to=yiboz@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=greearb@candelatech.com \
--cc=linux-wireless@vger.kernel.org \
--cc=zhichen@codeaurora.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox