From: Daniel Vetter <daniel@ffwll.ch>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org, stable@vger.kernel.org
Subject: Re: [PATCH] drm/i915; Only increment the user-pin-count after successfully pinning the bo
Date: Sun, 6 Jan 2013 18:27:59 +0100 [thread overview]
Message-ID: <20130106172759.GN5737@phenom.ffwll.local> (raw)
In-Reply-To: <1357122682-25314-1-git-send-email-chris@chris-wilson.co.uk>
On Wed, Jan 02, 2013 at 10:31:22AM +0000, Chris Wilson wrote:
> As along the error path we do not correct the user pin-count for the
> failure, we may end up with userspace believing that it has a pinned
> object at offset 0 (when interrupted by a signal for example).
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: stable@vger.kernel.org
pin_vs_interrupt in i-g-t? In any case, applied to -fixes, thanks for the
patch.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
prev parent reply other threads:[~2013-01-06 17:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-02 10:31 [PATCH] drm/i915; Only increment the user-pin-count after successfully pinning the bo Chris Wilson
2013-01-06 17:27 ` Daniel Vetter [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=20130106172759.GN5737@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=stable@vger.kernel.org \
/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