From: Alastair D'Silva <alastair@d-silva.org>
To: Ping-Ke Shih <pkshih@realtek.com>, linux-wireless@vger.kernel.org
Cc: Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
Ulf Hansson <ulfh@kernel.org>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Kalle Valo <kvalo@kernel.org>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v2] wifi: rtw88: sdio: Fix unhandled RX request interrupt storm
Date: Wed, 30 Sep 2026 19:18:32 +1000 [thread overview]
Message-ID: <46385ff62fd302329feafacfc37324a0510bb519.camel@d-silva.org> (raw)
In-Reply-To: <20260930090714.2779699-1-alastair@d-silva.org>
On Wed, 2026-09-30 at 19:07 +1000, Alastair D'Silva wrote:
> In rtw_sdio_handle_interrupt(), the HISR status register is cleared using
> Write-1-to-Clear (W1C) semantics. However, the driver masks out the
> REG_SDIO_HISR_RX_REQUEST bit in the local 'hisr' variable before writing
> it back, causing a 0 to be written to that bit. This prevents the RX
> request interrupt from being acknowledged and cleared in hardware, trapping
> the CPU core in an infinite interrupt storm loop (starving the RCU preempt
> kthread and locking up the system).
>
<snip>
> Fixes: 65371a3f14e7 ("wifi: rtw88: sdio: Add HCI implementation for SDIO based chipsets")
> Cc: stable@vger.kernel.org
> Signed-off-by: Alastair D'Silva <alastair@d-silva.org>
>
Apologies, I omitted the required attribution tag per Documentation/process/coding-assistants.rst:
Assisted-by: LLM
Maintainers, please feel free to add this when applying, or let me know if you would prefer a v3
respin.
Cheers,
--
Alastair D'Silva
next prev parent reply other threads:[~2026-09-30 9:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 9:07 Alastair D'Silva
2026-09-30 9:18 ` Alastair D'Silva [this message]
2026-09-30 10:06 ` Luka Gejak
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=46385ff62fd302329feafacfc37324a0510bb519.camel@d-silva.org \
--to=alastair@d-silva.org \
--cc=jernej.skrabec@gmail.com \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=pkshih@realtek.com \
--cc=stable@vger.kernel.org \
--cc=ulfh@kernel.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
all inboxes | Powered by JetHome®