From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.linuxfoundation.org ([140.211.169.12]:37654 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753379AbdBJVCv (ORCPT ); Fri, 10 Feb 2017 16:02:51 -0500 Date: Fri, 10 Feb 2017 22:02:43 +0100 From: Greg KH To: koos vriezen Cc: stable Subject: Re: FAILED: patch "[PATCH] drm/atomic: Fix double free in drm_atomic_state_default_clear" failed to apply to 4.9-stable tree Message-ID: <20170210210243.GA26049@kroah.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: stable-owner@vger.kernel.org List-ID: 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 . > > 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