From: Chris Wilson <chris@chris-wilson.co.uk>
To: Konstantin Belousov <kostikbel@gmail.com>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: struct_mutex leak in i915_load_gem_init ?
Date: Mon, 02 Apr 2012 22:01:46 +0100 [thread overview]
Message-ID: <1333400529_206992@CP5-2952> (raw)
In-Reply-To: <20120402203200.GZ2358@deviant.kiev.zoral.com.ua>
On Mon, 2 Apr 2012 23:32:00 +0300, Konstantin Belousov <kostikbel@gmail.com> wrote:
> Hi,
> it seems that in case of any i915_gem_init_aliasing_ppgtt() failure,
> after the commit d3ae08109d628d26615d7f7f4d8d53cdd8d71fd0, the struct_mutex
> lock leaks from i915_load_gem_init().
Right, I should have caught that before telling Daniel the patch was ok. :(
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-04-02 21:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-02 20:32 struct_mutex leak in i915_load_gem_init ? Konstantin Belousov
2012-04-02 21:01 ` Chris Wilson [this message]
2012-04-02 21:33 ` [PATCH] drm/i915: don't leak struct_mutex lock on ppgtt init failures Daniel Vetter
2012-04-03 8:15 ` Chris Wilson
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=1333400529_206992@CP5-2952 \
--to=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=kostikbel@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