From: w15303746062 <w15303746062@163.com>
To: airlied@redhat.com
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
x86@kernel.org, linux-pci@vger.kernel.org,
"Mingyu Wang" <25181214217@stu.xidian.edu.cn>
Subject: Re:[PATCH v2] char: agp: amd64 - fix broken error propagation in agp_amd64_probe()
Date: Thu, 4 Jun 2026 21:13:16 +0800 (CST) [thread overview]
Message-ID: <71742084.a1c9.19e92c4425c.Coremail.w15303746062@163.com> (raw)
In-Reply-To: <20260504074823.99377-1-w15303746062@163.com>
Hi Dave and everyone,
Just a gentle ping on this patch. It has been a month since v2 was submitted.
Please let me know if there are any questions, or if any further modifications are needed.
Thanks,
Mingyu
At 2026-05-04 15:48:23, w15303746062@163.com wrote:
>From: Mingyu Wang <25181214217@stu.xidian.edu.cn>
>
>A NULL pointer dereference was observed in the AMD64 AGP driver when
>running in a virtualized environment (e.g., QEMU/KVM) without a physical
>AMD Northbridge. The crash occurs in amd64_fetch_size() when attempting
>to dereference the pointer returned by node_to_amd_nb(0).
>
>The root cause of this crash is broken error propagation in
>agp_amd64_probe(). When no AMD Northbridges are found, cache_nbs()
>correctly returns -ENODEV. However, the probe function erroneously
>checked the return value against exactly -1, rather than < 0.
>
>As a result, the hardware absence error was masked, allowing the driver
>to improperly proceed with initialization. It eventually called
>agp_add_bridge(), which invokes amd64_fetch_size(). Since the hardware
>does not exist, node_to_amd_nb(0) returns NULL, leading to a General
>Protection Fault (GPF) when accessing its ->misc member.
>
>Fix the issue by correcting the error check in agp_amd64_probe() to
>abort properly when cache_nbs() returns any negative error code. This
>prevents the driver from erroneously proceeding without hardware, thereby
>resolving the subsequent NULL pointer dereference at its source.
>
>Signed-off-by: Mingyu Wang <25181214217@stu.xidian.edu.cn>
>---
>+ Changes in v2:
>+ - Dropped redundant NULL pointer checks in various initialization functions.
>+ - Fixed the actual root cause: broken error propagation in agp_amd64_probe()
>+ where it erroneously checked cache_nbs() against exactly -1 instead of < 0.
>+ (Thanks to Sashiko AI for the review feedback).
>+
> drivers/char/agp/amd64-agp.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
>diff --git a/drivers/char/agp/amd64-agp.c b/drivers/char/agp/amd64-agp.c
>index 2505df1f4e69..6741270e0a98 100644
>--- a/drivers/char/agp/amd64-agp.c
>+++ b/drivers/char/agp/amd64-agp.c
>@@ -546,7 +546,7 @@ static int agp_amd64_probe(struct pci_dev *pdev,
> /* Fill in the mode register */
> pci_read_config_dword(pdev, bridge->capndx+PCI_AGP_STATUS, &bridge->mode);
>
>- if (cache_nbs(pdev, cap_ptr) == -1) {
>+ if (cache_nbs(pdev, cap_ptr) < 0) {
> agp_put_bridge(bridge);
> return -ENODEV;
> }
>--
>2.34.1
next prev parent reply other threads:[~2026-06-04 13:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-04 7:48 [PATCH " w15303746062
2026-06-04 13:13 ` w15303746062 [this message]
2026-06-04 15:26 ` Lukas Wunner
2026-06-08 8:11 ` Lukas Wunner
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=71742084.a1c9.19e92c4425c.Coremail.w15303746062@163.com \
--to=w15303746062@163.com \
--cc=25181214217@stu.xidian.edu.cn \
--cc=airlied@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=x86@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®