From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Mingyu Wang <25181214217@stu.xidian.edu.cn>
Cc: Andi Kleen <ak@linux.intel.com>,
Alexander Martyniuk <alexevgmart@gmail.com>,
stable@vger.kernel.org, David Airlie <airlied@redhat.com>,
Sasha Levin <sashal@kernel.org>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Lukas Wunner <lukas@wunner.de>
Subject: Re: [PATCH 5.10/5.15/6.1/6.6/6.12] agp/amd64: Fix broken error propagation in agp_amd64_probe()
Date: Tue, 30 Jun 2026 11:21:51 +0200 [thread overview]
Message-ID: <2026063021-ripple-uranium-f24e@gregkh> (raw)
In-Reply-To: <5fbd827c-4c4d-4364-882c-41d2fe666fde@stu.xidian.edu.cn>
On Tue, Jun 30, 2026 at 09:23:50AM +0800, Mingyu Wang wrote:
>
> > What is special about this virtual environment? Nobody else
> > seems to have seen that in 20+ years.
> >
> > Or maybe the Fixes tag is not quite correct and something else more
> > recent has caused it.
>
> Hi Andi,
>
>
> You are right that normal users will not see this crash in the wild.
>
> The environment is a QEMU-based driver fuzzing framework. Rather than
> functionally emulating specific hardware, the framework extracts device
> matching information from the driver and synthesizes a mock PCI device just
> to trigger the driver's binding and initialization paths.
>
> In this case, the synthesized PCI device matched the AGP bridge's IDs,
> forcing `agp_amd64_probe()` to run. However, because this is a synthetic
> fuzzing environment, there was no physical or emulated AMD Northbridge
> present in the system.
Which means this is a contrivied environment that no one will actually
use, so there is no need to backport this change anywhere.
thanks,
greg k-h
prev parent reply other threads:[~2026-06-30 9:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-29 10:21 [PATCH 5.10/5.15/6.1/6.6/6.12] agp/amd64: Fix broken error propagation in agp_amd64_probe() Alexander Martyniuk
2026-06-29 15:40 ` Andi Kleen
2026-06-30 1:23 ` Mingyu Wang
2026-06-30 9:21 ` Greg Kroah-Hartman [this message]
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=2026063021-ripple-uranium-f24e@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=25181214217@stu.xidian.edu.cn \
--cc=airlied@redhat.com \
--cc=ak@linux.intel.com \
--cc=alexevgmart@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=sashal@kernel.org \
--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