Patch "etnaviv: fix gem object list corruption" has been added to the 4.13-stable tree
Subsystems (3)
This is a note to let you know that I've just added the patch titled
etnaviv: fix gem object list corruption
to the 4.13-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
etnaviv-fix-gem-object-list-corruption.patch
and it can be found in the queue-4.13 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree, please let <[email protected]> know about it.
Quoted 1 line
From
518417525f3652c12fb5fad6da4ade66c0072fa3Mon Sep 17 00:00:00 2001
From: Lucas Stach <[email protected]>
Date: Mon, 11 Sep 2017 15:29:31 +0200
Subject: etnaviv: fix gem object list corruption
From: Lucas Stach <[email protected]>
commit 518417525f3652c12fb5fad6da4ade66c0072fa3 upstream.
All manipulations of the gem_object list need to be protected by the list mutex, as GEM objects can be created and freed in parallel. This fixes a kernel memory corruption.
--- drivers/gpu/drm/etnaviv/etnaviv_gem.c | 3 +++ 1 file changed, 3 insertions(+)
drivers/gpu/drm/etnaviv/etnaviv_gem.c +3 -0
@@ -551,12 +551,15 @@ static const struct etnaviv_gem_ops etnavoid etnaviv_gem_free_object (struct drm_gem_object *obj) {struct etnaviv_gem_object *etnaviv_obj =to_etnaviv_bo (obj); +struct etnaviv_drm_private *priv = obj->dev->dev_private;struct etnaviv_vram_mapping *mapping, *tmp;/* object should not be active */ WARN_ON (is_active (etnaviv_obj)); +mutex_lock (&priv->gem_lock);list_del (&etnaviv_obj->gem_node); +mutex_unlock (&priv->gem_lock);list_for_each_entry_safe (mapping, tmp, &etnaviv_obj->vram_list, obj_node) {
Patches currently in stable-queue which might be from [email protected] are
queue-4.13/etnaviv-fix-gem-object-list-corruption.patch queue-4.13/etnaviv-fix-submit-error-path.patch