On Mon, Mar 18, 2013 at 09:02:57AM -0700, Greg KH wrote: > On Mon, Mar 18, 2013 at 10:22:19AM +0000, Chris Wilson wrote: > > From: Dmitry Rogozhkin <[email protected]> > > > > commit e79e0fe380847493266fba557217e2773c61bd1b upstream. > > > > 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. > > > > Note that this fixes i-g-t/tests/gem_threaded_tiled_access. > > > > Tested-by: Mika Kuoppala <[email protected]> > > Signed-off-by: Dmitry Rogozhkin <[email protected]> > > Reviewed-by: Chris Wilson <[email protected]> > > Signed-off-by: Daniel Vetter <[email protected]> > > --- > > drivers/gpu/drm/i915/i915_gem.c | 5 +++++ > > 1 file changed, 5 insertions(+) > > What stable release(s) should this be applied to?
The vulnerability exists right from the initial import of GEM, v2.6.29. It is only recently that userspace has become adventurous enough to hit the race condition. -Chris -- Chris Wilson, Intel Open Source Technology Centre -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
