aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/brcm2708/patches-4.19/950-0559-drm-v3d-Fix-a-use-after-free-race-accessing-the-sche.patch
diff options
context:
space:
mode:
authorÁlvaro Fernández Rojas <noltari@gmail.com>2019-09-19 16:43:19 +0200
committerÁlvaro Fernández Rojas <noltari@gmail.com>2019-09-19 17:38:18 +0200
commit4f8b350be0b90554c93908458a27be34e8b722ca (patch)
tree8b39d985a590db8cc4eb275d68496cfa212d5ede /target/linux/brcm2708/patches-4.19/950-0559-drm-v3d-Fix-a-use-after-free-race-accessing-the-sche.patch
parentb400179ca66647944a26f4d4b7b4fd53a3d2f0d1 (diff)
downloadupstream-4f8b350be0b90554c93908458a27be34e8b722ca.tar.gz
upstream-4f8b350be0b90554c93908458a27be34e8b722ca.tar.bz2
upstream-4f8b350be0b90554c93908458a27be34e8b722ca.zip
brcm2708: update to latest patches from RPi foundation
Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
Diffstat (limited to 'target/linux/brcm2708/patches-4.19/950-0559-drm-v3d-Fix-a-use-after-free-race-accessing-the-sche.patch')
-rw-r--r--target/linux/brcm2708/patches-4.19/950-0559-drm-v3d-Fix-a-use-after-free-race-accessing-the-sche.patch4
1 files changed, 2 insertions, 2 deletions
diff --git a/target/linux/brcm2708/patches-4.19/950-0559-drm-v3d-Fix-a-use-after-free-race-accessing-the-sche.patch b/target/linux/brcm2708/patches-4.19/950-0559-drm-v3d-Fix-a-use-after-free-race-accessing-the-sche.patch
index d727a64b72..1692bac2a0 100644
--- a/target/linux/brcm2708/patches-4.19/950-0559-drm-v3d-Fix-a-use-after-free-race-accessing-the-sche.patch
+++ b/target/linux/brcm2708/patches-4.19/950-0559-drm-v3d-Fix-a-use-after-free-race-accessing-the-sche.patch
@@ -1,7 +1,7 @@
-From 907c3b401f27e6ae6125abc043586b22b5f128ee Mon Sep 17 00:00:00 2001
+From f5f3df2b1746a9ba9420ae11988fc37a7b93691d Mon Sep 17 00:00:00 2001
From: Eric Anholt <eric@anholt.net>
Date: Fri, 28 Sep 2018 16:21:23 -0700
-Subject: [PATCH 559/782] drm/v3d: Fix a use-after-free race accessing the
+Subject: [PATCH 559/806] drm/v3d: Fix a use-after-free race accessing the
scheduler's fences.
Once we push the job, the scheduler could run it and free it. So, if