From: Kalle Valo <kvalo@kernel.org>
To: Ping-Ke Shih <pkshih@realtek.com>
Cc: Sergey Korolev <korolev.sergey@gmail.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: PROBLEM: kernel warns about voluntary context switch within RCU critical section in rtw88_usb
Date: Tue, 22 Aug 2023 08:41:45 +0300 [thread overview]
Message-ID: <87pm3fws4m.fsf@kernel.org> (raw)
In-Reply-To: <bfaa8714467a4954a045475e062f78b1@realtek.com> (Ping-Ke Shih's message of "Tue, 22 Aug 2023 01:47:34 +0000")
Ping-Ke Shih <pkshih@realtek.com> writes:
> From: Sergey Korolev <korolev.sergey@gmail.com>
> Sent: Monday, August 21, 2023 10:28 PM
> To: Ping-Ke Shih <pkshih@realtek.com>; Kalle Valo <kvalo@kernel.org>; linux-wireless@vger.kernel.org; linux-kernel@vger.kernel.org
> Subject: PROBLEM: kernel warns about voluntary context switch within RCU critical section in rtw88_usb
>>
>> Please note I use an unmodified driver from the upstream 28c11c29494f1b34e39641eead9c60a8bd26170d
>> ("wifi: rtw88: fix not entering PS mode after AP stops") build for 6.2 kernel (Ubuntu 23.04).
>
> I feel Martin has been addressed this problem during development of SDIO and USB
> by 8a1e2fd8e2da ("wifi: rtw88: Move register access from rtw_bf_assoc() outside the RCU")
> Please take a look if this patch is existing in your source.
Commit 8a1e2fd8e2da was merged to v6.3-rc1 so v6.2 won't have it.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2023-08-22 5:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+QjRnJ+YMdOM0OzwG+Pz8-mTPo5nZVioCjbz1xY0jVSGXBk7w@mail.gmail.com>
2023-08-22 1:47 ` PROBLEM: kernel warns about voluntary context switch within RCU critical section in rtw88_usb Ping-Ke Shih
2023-08-22 5:41 ` Kalle Valo [this message]
2023-08-22 5:46 ` Ping-Ke Shih
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=87pm3fws4m.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=korolev.sergey@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=pkshih@realtek.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.