On Wed, Feb 08, 2017 at 08:56:11PM +0100, koos vriezen wrote: > Hi, > > > The patch below does not apply to the 4.9-stable tree. > > If someone wants it applied there, or to any other stable or longterm > > tree, then please email the backport, including the original git commit > > id to <stable@xxxxxxxxxxxxxxx>. > > Commit beaf5af48034c9e2ebb8b2b1fb12dc4d8aeba99e "drm/fence: add > out-fences support" breaks backport of > 92c715fca907686f5298220ece53423e38ba3aed "drm/atomic: Fix double free > in drm_atomic_state_default_clear" > > Dunno if this double free can happen in 4.9, but the > drm_mode_atomic_ioctl function does only create call > drm_pending_vblank_event which sets event->base.fence || > event->base.file_priv. So 92c715fca907686f5298220ece53423e38ba3aed > makes sense. > > Attached my backport. Runs fine for a few days for me. Thanks for this, looks good! greg k-h -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html