From: Andi Shyti <andi.shyti@linux.intel.com>
To: Krzysztof Niemiec <krzysztof.niemiec@intel.com>
Cc: intel-gfx@lists.freedesktop.org, Andi Shyti <andi.shyti@linux.intel.com>
Subject: Re: [PATCH] drm/i915/gt: Delete sysfs entries for engines on driver unload
Date: Mon, 5 Aug 2024 23:30:14 +0100 [thread overview]
Message-ID: <ZrFSdvngs2arVQi-@ashyti-mobl2.lan> (raw)
In-Reply-To: <qx6a6di4z46gnfmi4an3x6io346ujncpoubcodxgs6l25veifc@piwwoizskuly>
On Mon, Aug 05, 2024 at 05:46:06PM +0200, Krzysztof Niemiec wrote:
> On 2024-08-01 at 17:40:48 GMT, Krzysztof Niemiec wrote:
> > While the sysfs entries for engines are added in intel_engines_init()
> > during driver load, the corresponding function intel_engines_release()
> > does not correctly get rid of them. This can lead to a UAF if, after
> > failed initialization (for example when gt is set wedged on init), we
> > try to access the engines.
> >
> > Empty the engines llist in intel_engines_release().
> >
> > Suggested-by: Chris Wilson <chris.p.wilson@linux.intel.com>
> > Signed-off-by: Krzysztof Niemiec <krzysztof.niemiec@intel.com>
...
> drm/i915/gt: Empty uabi engines list during intel_engines_release()
>
> While the uabi_engines_llist is populated in intel_engines_init() during
> driver load, the corresponding function intel_engines_release() does not
> correctly get rid of it. This can lead to a UAF if, after failed
> initialization (for example when gt is set wedged on init), we try to
> access the engines.
Pushed to drm-intel-gt-next with the updated commit.
Thanks,
Andi
prev parent reply other threads:[~2024-08-05 22:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-01 15:40 [PATCH] drm/i915/gt: Delete sysfs entries for engines on driver unload Krzysztof Niemiec
2024-08-01 16:36 ` ✓ Fi.CI.BAT: success for " Patchwork
2024-08-02 8:15 ` [PATCH] " Andi Shyti
2024-08-02 8:49 ` ✗ Fi.CI.IGT: failure for " Patchwork
2024-08-05 15:46 ` [PATCH] " Krzysztof Niemiec
2024-08-05 22:30 ` Andi Shyti [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=ZrFSdvngs2arVQi-@ashyti-mobl2.lan \
--to=andi.shyti@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=krzysztof.niemiec@intel.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