From: Greg KH <gregkh@linuxfoundation.org>
To: John Brooks <john@fastquake.com>
Cc: alexander.deucher@amd.com, christian.koenig@amd.com,
stable@vger.kernel.org
Subject: Re: [PATCH for 4.9] drm/ttm: Fix use-after-free in ttm_bo_clean_mm
Date: Mon, 24 Jul 2017 20:45:42 -0700 [thread overview]
Message-ID: <20170725034542.GA7471@kroah.com> (raw)
In-Reply-To: <20170725031530.GA26615@kitsune.fastquake.com>
On Tue, Jul 25, 2017 at 03:15:30AM +0000, John Brooks wrote:
> We unref the man->move fence in ttm_bo_clean_mm() and then call
> ttm_bo_force_list_clean() which waits on it, except the refcount is now
> zero so a warning is generated (or worse):
<snip>
Thanks for the backport!
greg k-h
prev parent reply other threads:[~2017-07-25 3:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-25 1:20 FAILED: patch "[PATCH] drm/ttm: Fix use-after-free in ttm_bo_clean_mm" failed to apply to 4.9-stable tree gregkh
2017-07-25 3:15 ` [PATCH for 4.9] drm/ttm: Fix use-after-free in ttm_bo_clean_mm John Brooks
2017-07-25 3:45 ` Greg KH [this message]
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=20170725034542.GA7471@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alexander.deucher@amd.com \
--cc=christian.koenig@amd.com \
--cc=john@fastquake.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).