Received-SPF: pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Sender: Larry Finger <larry.finger@gmail.com>
Message-ID: <f1e31e8e-f84e-3791-50fb-663a83c5c6e9@lwfinger.net>
Date:   Sun, 7 May 2023 19:55:35 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
 Thunderbird/102.10.1
Subject: Re: RCU WARNING Splat from rtw8822bu
To:     Ping-Ke Shih <pkshih@realtek.com>,
        Sascha Hauer <s.hauer@pengutronix.de>
Cc:     linux-wireless <linux-wireless@vger.kernel.org>
References: <d37638ad-27c8-e74e-ece1-c4de2eaccfa6@lwfinger.net>
 <3c2eabc6fc89496fb7e200d0710ba2f2@realtek.com>
Content-Language: en-US
From:   Larry Finger <Larry.Finger@lwfinger.net>
In-Reply-To: <3c2eabc6fc89496fb7e200d0710ba2f2@realtek.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk

On 5/7/23 19:49, Ping-Ke Shih wrote:
> The ieee80211_ops::sta_rc_update must be atomic, because ieee80211_chan_bw_change()
> holds rcu_read lock while calling drv_sta_rc_update(), so I think a simple way is
> to create a work to do original things. I will make a fix later.

Thanks.

I forgot to say that the WARNING did not cause the wifi connection to be 
dropped, thus the issue is one of log spamming, not stability.

Larry