[Bug 97381] New: kmem_cache_destroy - possible recursive locking detected

[bugzilla-daemon at freedesktop.org]

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

            Bug ID: 97381
           Summary: kmem_cache_destroy - possible recursive locking
                    detected
           Product: DRI
           Version: DRI git
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: matthew.auld at intel.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

Created attachment 125843
  --> https://bugs.freedesktop.org/attachment.cgi?id=125843&action=edit
dmesg

[  706.898063] =============================================
[  706.898078] [ INFO: possible recursive locking detected ]
[  706.898094] 4.8.0-rc2-drm-intel-debug+ #21 Tainted: G     U  W      
[  706.898108] ---------------------------------------------
[  706.898123] rmmod/1889 is trying to acquire lock:
[  706.898137]  (&(&n->list_lock)->rlock){-.-...}, at: [<ffffffff8151e7bb>]
get_partial_node+0x5b/0x460
[  706.898172] 
               but task is already holding lock:
[  706.898196]  (&(&n->list_lock)->rlock){-.-...}, at: [<ffffffff81525f1c>]
__kmem_cache_shutdown+0xac/0x670
[  706.898227] 
               other info that might help us debug this:
[  706.898252]  Possible unsafe locking scenario:

[  706.898276]        CPU0
[  706.898288]        ----
[  706.898300]   lock(&(&n->list_lock)->rlock);
[  706.898315]   lock(&(&n->list_lock)->rlock);
[  706.898330] 
                *** DEADLOCK ***

See attachment for the rest.

-- 
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: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20160817/1bdfb681/attachment.html>