From: Lukas Wunner <lukas@wunner.de>
To: Ahmed Salem <x0rw3ll@gmail.com>
Cc: airlied@redhat.com, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org,
linux-kernel-mentees@lists.linux.dev
Subject: Re: [RFC PATCH] amd64-agp: do not bind to pci driver if probing fails
Date: Sat, 21 Jun 2025 11:46:08 +0200 [thread overview]
Message-ID: <aFZ_YJH30f1WDneD@wunner.de> (raw)
In-Reply-To: <c5kqcudzrcafm24nr5ixgalhxdkxl3uoueerjlp6tbksj3hzy7@klytjugpkvdm>
On Sat, Jun 21, 2025 at 04:55:52AM +0300, Ahmed Salem wrote:
> --- a/drivers/char/agp/amd64-agp.c
> +++ b/drivers/char/agp/amd64-agp.c
> @@ -768,10 +768,15 @@ int __init agp_amd64_init(void)
>
> /* Look for any AGP bridge */
> agp_amd64_pci_driver.id_table = agp_amd64_pci_promisc_table;
> - err = driver_attach(&agp_amd64_pci_driver.driver);
> - if (err == 0 && agp_bridges_found == 0) {
> + if ((int *)agp_amd64_pci_driver.probe != 0) {
> pci_unregister_driver(&agp_amd64_pci_driver);
> err = -ENODEV;
> + } else {
> + err = driver_attach(&agp_amd64_pci_driver.driver);
> + if (err == 0 && agp_bridges_found == 0) {
> + pci_unregister_driver(&agp_amd64_pci_driver);
> + err = -ENODEV;
> + }
Is the "probe" member in agp_amd64_pci_driver overwritten with a
zero pointer anywhere? I don't see that it is, so it seems the
else-branch is never entered.
I had already prepared a fix for this, but waited for 0-day to
crunch through it. I've just submitted it, so that's what I had
in mind:
https://lore.kernel.org/r/f8ff40f35a9a5836d1371f60e85c09c5735e3c5e.1750497201.git.lukas@wunner.de/
Thanks,
Lukas
next prev parent reply other threads:[~2025-06-21 9:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-21 1:55 [RFC PATCH] amd64-agp: do not bind to pci driver if probing fails Ahmed Salem
2025-06-21 9:46 ` Lukas Wunner [this message]
2025-06-21 16:15 ` Ahmed Salem
2025-06-21 19:21 ` Lukas Wunner
2025-06-22 11:13 ` Ahmed Salem
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=aFZ_YJH30f1WDneD@wunner.de \
--to=lukas@wunner.de \
--cc=airlied@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=x0rw3ll@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox