From: Chris Wilson <chris@chris-wilson.co.uk>
To: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Cc: Daniel Vetter <daniel.vetter@intel.com>,
Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
David Airlie <airlied@linux.ie>,
intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [linux-mmotm] i915_gem_userptr_get_pages: possible circular locking dependency detected
Date: Tue, 14 Mar 2017 13:41:03 +0000 [thread overview]
Message-ID: <20170314134103.GI2118@nuc-i3427.alporthouse.com> (raw)
In-Reply-To: <20170314132109.GA388@tigerII.localdomain>
On Tue, Mar 14, 2017 at 10:21:09PM +0900, Sergey Senozhatsky wrote:
> Hello,
>
> [ 530.698622] ======================================================
> [ 530.698623] WARNING: possible circular locking dependency detected
> [ 530.698626] 4.11.0-rc2-mm1-dbg-00167-gdb8a9941614c-dirty #222 Not tainted
> [ 530.698627] ------------------------------------------------------
> [ 530.698628] Xorg/343 is trying to acquire lock:
> [ 530.698630] (&mm->mmap_sem){++++++}, at: [<ffffffffa057e085>] i915_gem_userptr_get_pages+0x60/0x29c [i915]
> [ 530.698702]
> but task is already holding lock:
> [ 530.698703] (&obj->mm.lock){+.+.+.}, at: [<ffffffffa0572d78>] __i915_gem_object_get_pages+0x21/0x62 [i915]
> [ 530.698763]
> which lock already depends on the new lock.
Yup, just seen it myself. This particular cycle is a non-issue, but
there is another possiblity for a mmap_sem recursion in the ggtt fault
handler.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
prev parent reply other threads:[~2017-03-14 13:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-14 13:21 Sergey Senozhatsky
2017-03-14 13:41 ` Chris Wilson [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=20170314134103.GI2118@nuc-i3427.alporthouse.com \
--to=chris@chris-wilson.co.uk \
--cc=airlied@linux.ie \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=sergey.senozhatsky@gmail.com \
/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
all inboxes | Powered by JetHome®