1 files changed, 39 insertions, 0 deletions
diff --git a/meta-amd-bsp/recipes-kernel/linux/linux-yocto-4.14.71/2157-drm-amdgpu-Potential-uninitialized-variable-in-amdgp.patch b/meta-amd-bsp/recipes-kernel/linux/linux-yocto-4.14.71/2157-drm-amdgpu-Potential-uninitialized-variable-in-amdgp.patch
new file mode 100644
index 00000000..1204f8e6
--- /dev/null
+++ b/meta-amd-bsp/recipes-kernel/linux/linux-yocto-4.14.71/2157-drm-amdgpu-Potential-uninitialized-variable-in-amdgp.patch
@@ -0,0 +1,39 @@
+From fe7018cde1f549eab818916013dae7cb60ff6b74 Mon Sep 17 00:00:00 2001
+From: Dan Carpenter <dan.carpenter@oracle.com>
+Date: Sat, 30 Sep 2017 11:14:13 +0300
+Subject: [PATCH 2157/4131] drm/amdgpu: Potential uninitialized variable in
+ amdgpu_vm_update_directories()
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+After commit ea09729c9302 ("drm/amdgpu: rework page directory filling
+v2") then it becomes a lot harder to verify that "r" is initialized.  My
+static checker complains and so I've reviewed the code.  It does look
+like it might be buggy... Anyway, it doesn't hurt to set "r" to zero
+at the start.
+
+Reviewed-by: Christian König <christian.koenig@amd.com>
+Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
+Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
+Cc: stable@vger.kernel.org
+---
+ drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c
+index bebf575..d4e8de3 100644
+--- a/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c
++++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c
+@@ -1253,7 +1253,7 @@ static void amdgpu_vm_invalidate_level(struct amdgpu_vm *vm,
+ int amdgpu_vm_update_directories(struct amdgpu_device *adev,
+ 				 struct amdgpu_vm *vm)
+ {
+-	int r;
++	int r = 0;
+ 
+ 	spin_lock(&vm->status_lock);
+ 	while (!list_empty(&vm->relocated)) {
+-- 
+2.7.4
+