On Wed, 3 Oct 2012 17:15:26 +0300, mika.kuoppala at intel.com wrote: > From: Dmitry Rogozhkin <dmitry.v.rogozhkin at intel.com> > > 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. > > Tested-by: Mika Kuoppala <mika.kuoppala at intel.com> > Signed-off-by: Dmitry Rogozhkin <dmitry.v.rogozhkin at intel.com> Fixes? Reported-by? I would order the case slightly different so that the comment block comes after EIO. Reviewed-by: Chris Wilson <chris at chris-wilson.co.uk> -Chris -- Chris Wilson, Intel Open Source Technology Centre
