[Bug 93248] [BAT BDW SKL] slab poisoning over module reload since build CI_DRM_862

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=93248

Daniel Vetter <daniel at ffwll.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #2 from Daniel Vetter <daniel at ffwll.ch> ---
commit af3302b90775ca3389c93ab31458d696e8a8fa60
Author: Daniel Vetter <daniel.vetter at ffwll.ch>
Date:   Fri Dec 4 17:27:15 2015 +0100

    Revert "drm/i915: Extend LRC pinning to cover GPU context writeback"

    This reverts commit 6d65ba943a2d1e4292a07ca7ddb6c5138b9efa5d.

    Mika Kuoppala traced down a use-after-free crash in module unload to
    this commit, because ring->last_context is leaked beyond when the
    context gets destroyed. Mika submitted a quick fix to patch that up in
    the context destruction code, but that's too much of a hack.

    The right fix is instead for the ring to hold a full reference onto
    it's last context, like we do for legacy contexts.

    Since this is causing a regression in BAT it gets reverted before we
    can close this.

    Cc: Nick Hoath <nicholas.hoath at intel.com>
    Cc: Daniel Vetter <daniel.vetter at ffwll.ch>
    Cc: David Gordon <david.s.gordon at intel.com>
    Cc: Chris Wilson <chris at chris-wilson.co.uk>
    Cc: Alex Dai <yu.dai at intel.com>
    Cc: Mika Kuoppala <mika.kuoppala at linux.intel.com>
    Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=93248
    Acked-by: Mika Kuoppala <mika.kuoppala at linux.intel.com>
    Signed-off-by: Daniel Vetter <daniel.vetter at intel.com>

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20151204/36425d59/attachment.html>