Commit e1d4ee0f authored Oct 20, 2013 by Rob Clark Committed by Tomi Valkeinen Mar 03, 2016

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 ("drm/i915: EBUSY status
handling added to i915_gem_fault()").

Signed-off-by: Rob Clark <robdclark@gmail.com>
Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>

parent be4f235c

drivers/gpu/drm/omapdrm/omap_gem.c

+5 −0

Original line number	Diff line number	Diff line
		@@ -578,6 +578,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;

Admin message