From: Jani Nikula <jani.nikula@linux.intel.com>
To: CJ <firefly0158@163.com>,
joonas.lahtinen@linux.intel.com, rodrigo.vivi@intel.com,
tursulin@ursulin.net, airlied@gmail.com, simona@ffwll.ch
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [BUG] drm/i915: general protection fault in i915_pci_probe on forced bind
Date: Mon, 14 Sep 2026 12:55:34 +0300 [thread overview]
Message-ID: <c830d55e4e1ed88571b15fbedee63de1c6f1ccd3@intel.com> (raw)
In-Reply-To: <3c467f81.7d23.1a09f0874aa.Coremail.firefly0158@163.com>
On Mon, 14 Sep 2026, CJ <firefly0158@163.com> wrote:
> I am reporting a general protection fault in the i915 PCI probe path, triggered
> by a syzkaller reproducer. The issue is reproducible with HEAD commit
> cee9395acd8043be0644b25c34bfa86623f2b935 (v7.3-rc1, Linux 7.3.0-rc1).
Try v7.3-rc2.
> The reproducer mounts sysfs, writes "i915" to the driver_override attribute of
> PCI device 0000:00:01.0, and then writes the device name to the i915 driver's
> bind attribute. This binds the i915 driver to a PCI device it was never meant
> to drive.
Is that a sane use case, though?
BR,
Jani.
--
Jani Nikula, Intel
prev parent reply other threads:[~2026-09-14 9:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-14 8:28 [BUG] drm/i915: general protection fault in i915_pci_probe on forced bind CJ
2026-09-14 9:55 ` Jani Nikula [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=c830d55e4e1ed88571b15fbedee63de1c6f1ccd3@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=firefly0158@163.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=joonas.lahtinen@linux.intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=simona@ffwll.ch \
--cc=tursulin@ursulin.net \
/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