From: Mika Kuoppala <mika.kuoppala@linux.intel.com>
To: Intel GFX <intel-gfx@lists.freedesktop.org>
Cc: Ben Widawsky <ben@bwidawsk.net>,
Ben Widawsky <benjamin.widawsky@intel.com>
Subject: Re: [PATCH] [v2] drm/i915/ppgtt: Never return a NULL context
Date: Thu, 02 Jan 2014 16:34:06 +0200 [thread overview]
Message-ID: <87vby2zc4h.fsf@gaia.fi.intel.com> (raw)
In-Reply-To: <1388555170-19936-1-git-send-email-benjamin.widawsky@intel.com>
Ben Widawsky <benjamin.widawsky@intel.com> writes:
> It makes all the code which calls into this function way too confusing.
>
> v2: Fix destroy IOCTL as well
>
callsite inside i915_gem_validate_context() and after it is called
in i915_gem_do_execbuffer() are still confusing as they seem to expect
NULL. Latter even tries to dig out error value from NULL.
-- Mika
> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=72903
> Signed-off-by: Ben Widawsky <ben@bwidawsk.net>
> ---
> drivers/gpu/drm/i915/i915_gem_context.c | 12 +++++++++---
> 1 file changed, 9 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_gem_context.c b/drivers/gpu/drm/i915/i915_gem_context.c
> index a90a0a1..f3ac9a2 100644
> --- a/drivers/gpu/drm/i915/i915_gem_context.c
> +++ b/drivers/gpu/drm/i915/i915_gem_context.c
> @@ -524,10 +524,16 @@ void i915_gem_context_close(struct drm_device *dev, struct drm_file *file)
> struct i915_hw_context *
> i915_gem_context_get(struct drm_i915_file_private *file_priv, u32 id)
> {
> + struct i915_hw_context *ctx;
> +
> if (!HAS_HW_CONTEXTS(file_priv->dev_priv->dev))
> return file_priv->private_default_ctx;
>
> - return (struct i915_hw_context *)idr_find(&file_priv->context_idr, id);
> + ctx = (struct i915_hw_context *)idr_find(&file_priv->context_idr, id);
> + if (!ctx)
> + return ERR_PTR(-ENOENT);
> +
> + return ctx;
> }
>
> static inline int
> @@ -774,9 +780,9 @@ int i915_gem_context_destroy_ioctl(struct drm_device *dev, void *data,
> return ret;
>
> ctx = i915_gem_context_get(file_priv, args->ctx_id);
> - if (!ctx) {
> + if (IS_ERR(ctx)) {
> mutex_unlock(&dev->struct_mutex);
> - return -ENOENT;
> + return PTR_ERR(ctx);
> }
>
> idr_remove(&ctx->file_priv->context_idr, ctx->id);
> --
> 1.8.5.2
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2014-01-02 14:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-19 23:22 [PATCH] drm/i915/ppgtt: Prevent NULL deref in reset ioctl Ben Widawsky
2013-12-20 6:05 ` Daniel Vetter
2013-12-20 6:55 ` Ben Widawsky
2013-12-20 14:11 ` Daniel Vetter
2013-12-20 14:37 ` Jani Nikula
2013-12-20 18:21 ` Ben Widawsky
2013-12-20 18:21 ` Ben Widawsky
2013-12-22 20:55 ` [PATCH] drm/i915/ppgtt: Never return a NULL context Ben Widawsky
2014-01-01 5:46 ` [PATCH] [v2] " Ben Widawsky
2014-01-02 14:34 ` Mika Kuoppala [this message]
[not found] <to=1388555170-19936-1-git-send-email-benjamin.widawsky@intel.com>
2014-01-03 5:50 ` Ben Widawsky
2014-01-03 12:07 ` Mika Kuoppala
2014-01-07 7:51 ` Daniel Vetter
[not found] ` <CALNAZXq8EZ4Wmq2ONz08gNFcEv4Bi-JzBasEvnAKWEfEWyf_xw@mail.gmail.com>
[not found] ` <CAKMK7uE9aai27U7jwGe0jK5AzjxKx40z8VyS1D4mr__a5x-Qeg@mail.gmail.com>
2014-01-10 23:20 ` Daniel Vetter
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=87vby2zc4h.fsf@gaia.fi.intel.com \
--to=mika.kuoppala@linux.intel.com \
--cc=ben@bwidawsk.net \
--cc=benjamin.widawsky@intel.com \
--cc=intel-gfx@lists.freedesktop.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