Skip to contentSkip to conversation

drm/amdkfd: Fix potential NULL pointer dereferences

PATCH Superseded Gustavo A. R. Silva 2 participants 4 messages Jan 10, 2018

Subsystems (3)

v1 of 2 Superseded Latest is v2 →

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 drm/amdkfd: Fix potential NULL pointer dereferences

In case kfd_get_process_device_data returns null, there are some null pointer dereferences in functions kfd_bind_processes_to_device and kfd_unbind_processes_from_device.

Fix this by null checking pdd before dereferencing it.

Addresses-Coverity-ID: 1463794 ("Dereference null return value")
Addresses-Coverity-ID: 1463772 ("Dereference null return value")

---
 drivers/gpu/drm/amd/amdkfd/kfd_process.c | 12 ++++++++++++
 1 file changed, 12 insertions(+)
drivers/gpu/drm/amd/amdkfd/kfd_process.c +12 -0
index a22fb071..29d51d5 100644
@@ -461,6 +461,13 @@ int kfd_bind_processes_to_device(struct kfd_dev *dev)
 	hash_for_each_rcu(kfd_processes_table, temp, p, kfd_processes) {
 		mutex_lock(&p->mutex);
 		pdd = kfd_get_process_device_data(dev, p);
+
+		if (!pdd) {
+			pr_err("Process device data doesn't exist\n");
+			mutex_unlock(&p->mutex);
+			return -EFAULT;
+		}
+
 		if (pdd->bound != PDD_BOUND_SUSPENDED) {
 			mutex_unlock(&p->mutex);
 			continue;
@@ -501,6 +508,11 @@ void kfd_unbind_processes_from_device(struct kfd_dev *dev)
 		mutex_lock(&p->mutex);
 		pdd = kfd_get_process_device_data(dev, p);
 
+		if (!pdd) {
+			mutex_unlock(&p->mutex);
+			return;
+		}
+
 		if (pdd->bound == PDD_BOUND)
 			pdd->bound = PDD_BOUND_SUSPENDED;
 		mutex_unlock(&p->mutex);
Signature · 1 line
2.7.4
maintainer
#1 lore raw

Hi Gustavo,

Thanks for catching that. When returning a fault, I think you also need to srcu_read_unlock(&kfd_processes_srcu, idx).

However, instead of returning an error, I think I'd prefer to skip PDDs that can't be found with continue statements. That way others would still suspend and resume successfully. Maybe just print a WARN_ON for PDDs that aren't found, because that's an unexpected situation, currently. Maybe in the future it could be normal thing if we ever support GPU hotplug.

Regards,
  Felix

Quoted 33 lines · Gustavo A. R. Silva

In case kfd_get_process_device_data returns null, there are some null pointer dereferences in functions kfd_bind_processes_to_device and kfd_unbind_processes_from_device.

Fix this by null checking pdd before dereferencing it.

Addresses-Coverity-ID: 1463794 ("Dereference null return value")
Addresses-Coverity-ID: 1463772 ("Dereference null return value")

---
 drivers/gpu/drm/amd/amdkfd/kfd_process.c | 12 ++++++++++++
 1 file changed, 12 insertions(+)
drivers/gpu/drm/amd/amdkfd/kfd_process.c +7 -0
index a22fb071..29d51d5 100644
@@ -461,6 +461,13 @@ int kfd_bind_processes_to_device(struct kfd_dev *dev)
 	hash_for_each_rcu(kfd_processes_table, temp, p, kfd_processes) {
 		mutex_lock(&p->mutex);
 		pdd = kfd_get_process_device_data(dev, p);
+
+		if (!pdd) {
+			pr_err("Process device data doesn't exist\n");
+			mutex_unlock(&p->mutex);
+			return -EFAULT;
+		}
+
 		if (pdd->bound != PDD_BOUND_SUSPENDED) {
 			mutex_unlock(&p->mutex);
 			continue;
@@ -501,6 +508,11 @@ void kfd_unbind_processes_from_device(struct kfd_dev *dev)
 		mutex_lock(&p->mutex);

drivers/gpu/drm/amd/amdkfd/kfd_process.c void kfd_unbind_processes_from_device(struct kfd_dev *dev) · line 518

Quoted 10 lines
drivers/gpu/drm/amd/amdkfd/kfd_process.c +5 -0
 		pdd = kfd_get_process_device_data(dev, p);
 
+		if (!pdd) {
+			mutex_unlock(&p->mutex);
+			return;
+		}
+
 		if (pdd->bound == PDD_BOUND)
 			pdd->bound = PDD_BOUND_SUSPENDED;
 		mutex_unlock(&p->mutex);

_______________________________________________
amd-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

#2 lore raw

Hi Felix,

Quoting Felix Kuehling <[email protected]>:

Quoted 5 lines

Hi Gustavo,

Thanks for catching that. When returning a fault, I think you also need to srcu_read_unlock(&kfd_processes_srcu, idx).

Quoted 7 lines

However, instead of returning an error, I think I'd prefer to skip PDDs that can't be found with continue statements. That way others would still suspend and resume successfully. Maybe just print a WARN_ON for PDDs that aren't found, because that's an unexpected situation, currently. Maybe in the future it could be normal thing if we ever support GPU hotplug.

I got it. In that case, what do you think about the following patch instead?

index a22fb071..4ff5f0f 100644

drivers/gpu/drm/amd/amdkfd/kfd_process.c +7 -1
@@ -461,7 +461,8 @@ int kfd_bind_processes_to_device(struct kfd_dev *dev)
        hash_for_each_rcu(kfd_processes_table, temp, p, kfd_processes) {
                mutex_lock(&p->mutex);
                pdd = kfd_get_process_device_data(dev, p);
-               if (pdd->bound != PDD_BOUND_SUSPENDED) {
+
+               if (WARN_ON(!pdd) || pdd->bound != PDD_BOUND_SUSPENDED) {
                        mutex_unlock(&p->mutex);
                        continue;
                }
@@ -501,6 +502,11 @@ void kfd_unbind_processes_from_device(struct kfd_dev *dev)
                mutex_lock(&p->mutex);
                pdd = kfd_get_process_device_data(dev, p);
 
+               if (WARN_ON(!pdd)) {
+                       mutex_unlock(&p->mutex);
+                       continue;
+               }
+
                if (pdd->bound == PDD_BOUND)
                        pdd->bound = PDD_BOUND_SUSPENDED;
                mutex_unlock(&p->mutex);

Thank you for the feedback.
--
Gustavo

Quoted 49 lines

Regards,
  Felix

Quoted 44 lines · Gustavo A. R. Silva

In case kfd_get_process_device_data returns null, there are some null pointer dereferences in functions kfd_bind_processes_to_device and kfd_unbind_processes_from_device.

Fix this by null checking pdd before dereferencing it.

Addresses-Coverity-ID: 1463794 ("Dereference null return value")
Addresses-Coverity-ID: 1463772 ("Dereference null return value")

---
 drivers/gpu/drm/amd/amdkfd/kfd_process.c | 12 ++++++++++++
 1 file changed, 12 insertions(+)
drivers/gpu/drm/amd/amdkfd/kfd_process.c +12 -0
index a22fb071..29d51d5 100644
@@ -461,6 +461,13 @@ int kfd_bind_processes_to_device(struct kfd_dev *dev)
 	hash_for_each_rcu(kfd_processes_table, temp, p, kfd_processes) {
 		mutex_lock(&p->mutex);
 		pdd = kfd_get_process_device_data(dev, p);
+
+		if (!pdd) {
+			pr_err("Process device data doesn't exist\n");
+			mutex_unlock(&p->mutex);
+			return -EFAULT;
+		}
+
 		if (pdd->bound != PDD_BOUND_SUSPENDED) {
 			mutex_unlock(&p->mutex);
 			continue;
@@ -501,6 +508,11 @@ void kfd_unbind_processes_from_device(struct  
 kfd_dev *dev)
 		mutex_lock(&p->mutex);
 		pdd = kfd_get_process_device_data(dev, p);
 
+		if (!pdd) {
+			mutex_unlock(&p->mutex);
+			return;
+		}
+
 		if (pdd->bound == PDD_BOUND)
 			pdd->bound = PDD_BOUND_SUSPENDED;

mutex_unlock(&p->mutex);

maintainer
#3 lore raw

Yeah, this looks good to me.

Regards,
  Felix

Quoted 48 lines · Gustavo A. R. Silva

Hi Felix,

Quoting Felix Kuehling <[email protected]>:

Quoted 5 lines

Hi Gustavo,

Thanks for catching that. When returning a fault, I think you also need to srcu_read_unlock(&kfd_processes_srcu, idx).

Quoted 7 lines

However, instead of returning an error, I think I'd prefer to skip PDDs that can't be found with continue statements. That way others would still suspend and resume successfully. Maybe just print a WARN_ON for PDDs that aren't found, because that's an unexpected situation, currently. Maybe in the future it could be normal thing if we ever support GPU hotplug.

I got it. In that case, what do you think about the following patch instead?

index a22fb071..4ff5f0f 100644

drivers/gpu/drm/amd/amdkfd/kfd_process.c +7 -1
@@ -461,7 +461,8 @@ int kfd_bind_processes_to_device(struct kfd_dev *dev)
         hash_for_each_rcu(kfd_processes_table, temp, p, kfd_processes) {
                 mutex_lock(&p->mutex);
                 pdd = kfd_get_process_device_data(dev, p);
-               if (pdd->bound != PDD_BOUND_SUSPENDED) {
+
+               if (WARN_ON(!pdd) || pdd->bound != PDD_BOUND_SUSPENDED) {
                         mutex_unlock(&p->mutex);
                         continue;
                 }
@@ -501,6 +502,11 @@ void kfd_unbind_processes_from_device(struct
 kfd_dev *dev)
                 mutex_lock(&p->mutex);
                 pdd = kfd_get_process_device_data(dev, p);
 
+               if (WARN_ON(!pdd)) {
+                       mutex_unlock(&p->mutex);
+                       continue;
+               }
+
                 if (pdd->bound == PDD_BOUND)
                         pdd->bound = PDD_BOUND_SUSPENDED;

                mutex_unlock(&p->mutex);

Quoted 61 lines

Thank you for the feedback.

Signature · 1 line
Gustavo
Quoted 43 lines

Regards,
  Felix

Quoted 38 lines · Gustavo A. R. Silva

In case kfd_get_process_device_data returns null, there are some null pointer dereferences in functions kfd_bind_processes_to_device and kfd_unbind_processes_from_device.

Fix this by null checking pdd before dereferencing it.

Addresses-Coverity-ID: 1463794 ("Dereference null return value")
Addresses-Coverity-ID: 1463772 ("Dereference null return value")

---
 drivers/gpu/drm/amd/amdkfd/kfd_process.c | 12 ++++++++++++

 1 file changed, 12 insertions(+)
drivers/gpu/drm/amd/amdkfd/kfd_process.c +7 -0
index a22fb071..29d51d5 100644
@@ -461,6 +461,13 @@ int kfd_bind_processes_to_device(struct kfd_dev
 *dev)
      hash_for_each_rcu(kfd_processes_table, temp, p, kfd_processes) {
          mutex_lock(&p->mutex);
          pdd = kfd_get_process_device_data(dev, p);
+
+        if (!pdd) {
+            pr_err("Process device data doesn't exist\n");
+            mutex_unlock(&p->mutex);
+            return -EFAULT;
+        }
+
          if (pdd->bound != PDD_BOUND_SUSPENDED) {
              mutex_unlock(&p->mutex);

             continue;

drivers/gpu/drm/amd/amdkfd/kfd_process.c +0 -0
@@ -501,6 +508,11 @@ void kfd_unbind_processes_from_device(struct
 kfd_dev *dev)
          mutex_lock(&p->mutex);
          pdd = kfd_get_process_device_data(dev, p);
 
Quoted 8 lines
Quoted 8 lines
drivers/gpu/drm/amd/amdkfd/kfd_process.c +5 -0
+        if (!pdd) {
+            mutex_unlock(&p->mutex);
+            return;
+        }
+
          if (pdd->bound == PDD_BOUND)
              pdd->bound = PDD_BOUND_SUSPENDED;

         mutex_unlock(&p->mutex);

_______________________________________________
dri-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dri-devel