From: Daniel Vetter <daniel@ffwll.ch>
To: Chris Wilson <chris@chris-wilson.co.uk>,
Mika Kuoppala <mika.kuoppala@linux.intel.com>,
intel-gfx@lists.freedesktop.org, stable@vger.kernel.org
Subject: Re: [PATCH] drm/i915: Fix erroneous dereference of batch_obj inside reset_status
Date: Thu, 12 Dec 2013 10:54:20 +0100 [thread overview]
Message-ID: <20131212095420.GG9804@phenom.ffwll.local> (raw)
In-Reply-To: <20131205162201.GI3197@nuc-i3427.alporthouse.com>
On Thu, Dec 05, 2013 at 04:22:02PM +0000, Chris Wilson wrote:
> On Thu, Dec 05, 2013 at 06:07:27PM +0200, Mika Kuoppala wrote:
> > Chris Wilson <chris@chris-wilson.co.uk> writes:
> >
> > > As the rings may be processed and their requests deallocated in a
> > > different order to the natural retirement during a reset,
> > >
> > > /* Whilst this request exists, batch_obj will be on the
> > > * active_list, and so will hold the active reference. Only when this
> > > * request is retired will the the batch_obj be moved onto the
> > > * inactive_list and lose its active reference. Hence we do not need
> > > * to explicitly hold another reference here.
> > > */
> > >
> > > is violated, and the batch_obj may be dereferenced after it had been
> > > freed on another ring. This can be simply avoided by processing the
> > > status update prior to deallocating any requests.
> > >
> > > Fixes regression (a possible OOPS following a GPU hang) from
> > > commit aa60c664e6df502578454621c3a9b1f087ff8d25
> > > Author: Mika Kuoppala <mika.kuoppala@linux.intel.com>
> > > Date: Wed Jun 12 15:13:20 2013 +0300
> > >
> > > drm/i915: find guilty batch buffer on ring resets
> > >
> > > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> > > Cc: Mika Kuoppala <mika.kuoppala@intel.com>
> > > Cc: stable@vger.kernel.org
> >
> > Passes the igt/gem_reset_stats/close-pending-fork and
> > doesn't affect the fast path.
> >
> > Reviewed-by: Mika Kuoppala <mika.kuoppala@intel.com>
>
> For reference, this is the comment I added upon request:
>
> @@ -2502,8 +2508,15 @@ void i915_gem_reset(struct drm_device *dev)
> struct intel_ring_buffer *ring;
> int i;
>
> + /* Before we free the objects from the requests, we need to inspect
> + * them for finding the guilty party. As the requests only borrow
> + * their reference to the objects, the inspection must be done first.
> + */
> + for_each_ring(ring, dev_priv, i)
> + i915_gem_reset_ring_status(dev_priv, ring);
> +
> for_each_ring(ring, dev_priv, i)
> - i915_gem_reset_ring_lists(dev_priv, ring);
> + i915_gem_reset_ring_cleanup(dev_priv, ring);
>
> i915_gem_cleanup_ringbuffer(dev);
QA didn't hit this bug since the test wasn't added to the right make
target. With that sorted I've now merged this patch (including comment) to
-fixes.
Thanks, Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
prev parent reply other threads:[~2013-12-12 9:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-04 11:37 [PATCH] drm/i915: Fix erroneous dereference of batch_obj inside reset_status Chris Wilson
2013-12-04 12:18 ` Daniel Vetter
2013-12-04 12:32 ` [Intel-gfx] " Chris Wilson
2013-12-05 16:07 ` Mika Kuoppala
2013-12-05 16:22 ` Chris Wilson
2013-12-12 9:54 ` Daniel Vetter [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=20131212095420.GG9804@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mika.kuoppala@linux.intel.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