Skip to contentSkip to conversation

drm/omap: EBUSY status handling in omap_gem_fault()

PATCH New Rob Clark 1 participant 1 message Oct 20, 2013

Subsystems (3)
lore
Share & tools
lore

Rob Clark

author
#0 lore raw

PATCH 1/1 drm/omap: EBUSY status handling in omap_gem_fault()

Subsequent threads returning EBUSY from vm_insert_pfn() was not handled correctly. As a result concurrent access from new threads to mmapped data caused SIGBUS.

See e79e0fe3

---
 drivers/gpu/drm/omapdrm/omap_gem.c | 5 +++++
 1 file changed, 5 insertions(+)
drivers/gpu/drm/omapdrm/omap_gem.c +5 -0
index 533f6eb..435c6b1 100644
@@ -542,6 +542,11 @@ fail:
 	case 0:
 	case -ERESTARTSYS:
 	case -EINTR:
+	case -EBUSY:
+		/*
+		 * EBUSY is ok: this just means that another thread
+		 * already did the job.
+		 */
 		return VM_FAULT_NOPAGE;
 	case -ENOMEM:
 		return VM_FAULT_OOM;
Signature · 1 line
1.8.3.1