From: Greg KH <gregkh@linuxfoundation.org>
To: koos vriezen <koos.vriezen@gmail.com>
Cc: stable <stable@vger.kernel.org>
Subject: Re: FAILED: patch "[PATCH] drm/atomic: Fix double free in drm_atomic_state_default_clear" failed to apply to 4.9-stable tree
Date: Fri, 10 Feb 2017 22:02:43 +0100 [thread overview]
Message-ID: <20170210210243.GA26049@kroah.com> (raw)
In-Reply-To: <CAGCbPWRCEqARmDE8UcN3LUQfE96y0-TO4DGhc0XputpPCwveeA@mail.gmail.com>
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
next prev parent reply other threads:[~2017-02-10 21:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-08 19:56 FAILED: patch "[PATCH] drm/atomic: Fix double free in drm_atomic_state_default_clear" failed to apply to 4.9-stable tree koos vriezen
2017-02-10 21:02 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-02-04 9:15 gregkh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170210210243.GA26049@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=koos.vriezen@gmail.com \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).