From: Ping-Ke Shih <pkshih@realtek.com>
To: Fedor Pchelkin <pchelkin@ispras.ru>
Cc: Jian-Hong Pan <jhp@endlessos.org>, Kalle Valo <kvalo@kernel.org>,
"Kai-Heng Feng" <kai.heng.feng@canonical.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Bitterblue Smith <rtl8821cerfe2@gmail.com>,
Dmitry Antipov <dmantipov@yandex.ru>,
"lvc-project@linuxtesting.org" <lvc-project@linuxtesting.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: RE: [PATCH rtw-next] wifi: rtw88: check for PCI upstream bridge existence
Date: Mon, 23 Feb 2026 02:09:24 +0000 [thread overview]
Message-ID: <42615e24cf4a4e19979765b3bdf07d8c@realtek.com> (raw)
In-Reply-To: <20260220094730.49791-1-pchelkin@ispras.ru>
Fedor Pchelkin <pchelkin@ispras.ru> wrote:
> pci_upstream_bridge() returns NULL if the device is on a root bus. If
> 8821CE is installed in the system with such a PCI topology, the probing
> routine will crash. This has probably been unnoticed as 8821CE is mostly
> supplied in laptops where there is a PCI-to-PCI bridge located upstream
> from the device. However the card might be installed on a system with
> different configuration.
>
> Check if the bridge does exist for the specific workaround to be applied.
>
> Found by Linux Verification Center (linuxtesting.org) with Svace static
> analysis tool.
>
> Fixes: 24f5e38a13b5 ("rtw88: Disable PCIe ASPM while doing NAPI poll on 8821CE")
> Cc: stable@vger.kernel.org
> Signed-off-by: Fedor Pchelkin <pchelkin@ispras.ru>
Acked-by: Ping-Ke Shih <pkshih@realtek.com>
next prev parent reply other threads:[~2026-02-23 2:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-20 9:47 [PATCH rtw-next] wifi: rtw88: check for PCI upstream bridge existence Fedor Pchelkin
2026-02-23 2:09 ` Ping-Ke Shih [this message]
2026-03-03 2:54 ` 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=42615e24cf4a4e19979765b3bdf07d8c@realtek.com \
--to=pkshih@realtek.com \
--cc=dmantipov@yandex.ru \
--cc=jhp@endlessos.org \
--cc=kai.heng.feng@canonical.com \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=pchelkin@ispras.ru \
--cc=rtl8821cerfe2@gmail.com \
--cc=stable@vger.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