[Bug 103730] [CI] igt at drv_selftest@live_context - dmesg-warn - WARNING: possible circular locking dependency detected

[bugzilla-daemon at freedesktop.org]

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

--- Comment #1 from Chris Wilson <chris at chris-wilson.co.uk> ---
What is this trace

               -> #1 (&mm->mmap_sem){++++}:
[ 1366.741362]        lock_acquire+0xb0/0x200
[ 1366.741364]        down_write+0x3b/0x70
[ 1366.741364]        0xffffffffa019a1ea
[ 1366.741365]        0xffffffffa019a3bd
[ 1366.741366]        0xffffffffa016bd3e
[ 1366.741368]        drm_gem_prime_handle_to_fd+0x18e/0x1c0
[ 1366.741370]        drm_prime_handle_to_fd_ioctl+0x44/0x60
[ 1366.741371]        drm_ioctl_kernel+0x69/0xb0
[ 1366.741372]        drm_ioctl+0x2f9/0x3d0
[ 1366.741375]        do_vfs_ioctl+0x94/0x670
[ 1366.741376]        SyS_ioctl+0x41/0x70
[ 1366.741379]        entry_SYSCALL_64_fastpath+0x1c/0xb1

? That makes no sense (we never need the write lock on mmap_sem inside
handle_to_fd, afaik). I do believe lockdep has lost track its marbles, possibly
due to a hash conflict due to the many module reloads.

-- 
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/20171114/d2d7b570/attachment.html>