From: Tomas Elf <tomas.elf@intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Intel-GFX@Lists.FreeDesktop.Org
Subject: Re: [PATCH 4/8] drm/i915: NULL checking when capturing buffer objects during error state capture
Date: Fri, 09 Oct 2015 12:45:46 +0100 [thread overview]
Message-ID: <5617A8EA.8040003@intel.com> (raw)
In-Reply-To: <20151009083211.GI26718@phenom.ffwll.local>
On 09/10/2015 09:32, Daniel Vetter wrote:
> On Thu, Oct 08, 2015 at 07:31:36PM +0100, Tomas Elf wrote:
>> In the past vmas have sometimes turned out to be NULL when capturing buffer
>> objects during error state capture. To avoid NULL pointer exceptions throw a
>> WARNING and exit early and be prepared for the error state not being fully
>> accurate following this point.
>>
>> Signed-off-by: Tomas Elf <tomas.elf@intel.com>
>> ---
>> drivers/gpu/drm/i915/i915_gpu_error.c | 10 +++++++++-
>> 1 file changed, 9 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/i915/i915_gpu_error.c b/drivers/gpu/drm/i915/i915_gpu_error.c
>> index cc75ca4..ae24971 100644
>> --- a/drivers/gpu/drm/i915/i915_gpu_error.c
>> +++ b/drivers/gpu/drm/i915/i915_gpu_error.c
>> @@ -691,9 +691,17 @@ unwind:
>> static void capture_bo(struct drm_i915_error_buffer *err,
>> struct i915_vma *vma)
>> {
>> - struct drm_i915_gem_object *obj = vma->obj;
>> + struct drm_i915_gem_object *obj;
>> int i;
>>
>> + if (WARN_ON(!vma))
>> + return;
>
> If we rcu-protect the vma lists and vmas themselves then this can't
> happen.
>
>> +
>> + if (WARN_ON(!vma->obj))
>> + return;
>
> Again we probably need to rcu-protect this, and more important we need to
> make sure the compiler doesn't do crap. So
>
> obj = rcu_derefence(vma->obj)
> if (!obj)
> return;
>
> Ofc obj then can also only be released with kfree_rcu.
> -Daniel
Awesome! Let's go with that solution then.
Thanks,
Tomas
>
>> +
>> + obj = vma->obj;
>> +
>> err->size = obj->base.size;
>> err->name = obj->base.name;
>> for (i = 0; i < I915_NUM_RINGS; i++)
>> --
>> 1.9.1
>>
>> _______________________________________________
>> Intel-gfx mailing list
>> Intel-gfx@lists.freedesktop.org
>> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-10-09 11:45 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-08 18:31 [PATCH 0/8] Stability improvements to error state capture Tomas Elf
2015-10-08 18:31 ` [PATCH 1/8] drm/i915: Early exit from semaphore_waits_for for execlist mode Tomas Elf
2015-10-08 18:31 ` [PATCH 2/8] drm/i915: Migrate to safe iterators in error state capture Tomas Elf
2015-10-09 7:49 ` Chris Wilson
2015-10-09 11:38 ` Tomas Elf
2015-10-09 8:27 ` Daniel Vetter
2015-10-09 11:40 ` Tomas Elf
2015-10-13 11:37 ` Daniel Vetter
2015-10-13 11:47 ` Chris Wilson
2015-10-08 18:31 ` [PATCH 3/8] drm/i915: Cope with request list state change during " Tomas Elf
2015-10-09 7:48 ` Chris Wilson
2015-10-09 11:25 ` Tomas Elf
2015-10-13 11:39 ` Daniel Vetter
2015-10-14 11:46 ` Tomas Elf
2015-10-14 12:45 ` Daniel Vetter
2015-10-09 8:28 ` Daniel Vetter
2015-10-09 11:45 ` Tomas Elf
2015-10-13 11:40 ` Daniel Vetter
2015-10-08 18:31 ` [PATCH 4/8] drm/i915: NULL checking when capturing buffer objects " Tomas Elf
2015-10-09 7:49 ` Chris Wilson
2015-10-09 11:34 ` Tomas Elf
2015-10-09 8:32 ` Daniel Vetter
2015-10-09 8:47 ` Chris Wilson
2015-10-09 11:52 ` Tomas Elf
2015-10-09 11:45 ` Tomas Elf [this message]
2015-10-08 18:31 ` [PATCH 5/8] drm/i915: vma NULL pointer check Tomas Elf
2015-10-09 7:48 ` Chris Wilson
2015-10-09 11:30 ` Tomas Elf
2015-10-09 11:59 ` Chris Wilson
2015-10-13 11:43 ` Daniel Vetter
2015-10-09 8:33 ` Daniel Vetter
2015-10-09 11:46 ` Tomas Elf
2015-10-08 18:31 ` [PATCH 6/8] drm/i915: Use safe list iterators Tomas Elf
2015-10-09 7:41 ` Chris Wilson
2015-10-09 10:27 ` Tomas Elf
2015-10-09 10:38 ` Chris Wilson
2015-10-09 12:00 ` Tomas Elf
2015-10-08 18:31 ` [PATCH 7/8] drm/i915: Grab execlist spinlock to avoid post-reset concurrency issues Tomas Elf
2015-10-09 7:45 ` Chris Wilson
2015-10-09 10:28 ` Tomas Elf
2015-10-09 8:38 ` Daniel Vetter
2015-10-09 8:45 ` Chris Wilson
2015-10-13 11:46 ` Daniel Vetter
2015-10-13 11:45 ` Chris Wilson
2015-10-13 13:46 ` Daniel Vetter
2015-10-13 14:00 ` Chris Wilson
2015-10-19 15:32 ` [PATCH v2 " Tomas Elf
2015-10-22 16:49 ` Dave Gordon
2015-10-22 17:35 ` Daniel Vetter
2015-10-23 8:42 ` Tvrtko Ursulin
2015-10-23 8:59 ` Daniel Vetter
2015-10-23 11:02 ` Tomas Elf
2015-10-23 12:49 ` Dave Gordon
2015-10-23 13:08 ` [PATCH v3 " Tomas Elf
2015-10-23 14:53 ` Daniel, Thomas
2015-10-23 17:02 ` [PATCH] drm/i915: Update to post-reset execlist queue clean-up Tomas Elf
2015-12-01 11:46 ` Tvrtko Ursulin
2015-12-11 14:14 ` Dave Gordon
2015-12-11 16:40 ` Daniel Vetter
2015-12-14 10:21 ` Mika Kuoppala
2015-10-08 18:31 ` [PATCH 8/8] drm/i915: NULL check of unpin_work Tomas Elf
2015-10-09 7:46 ` Chris Wilson
2015-10-09 8:39 ` Daniel Vetter
2015-10-09 11:50 ` Tomas Elf
2015-10-09 10:30 ` Tomas Elf
2015-10-09 10:44 ` Chris Wilson
2015-10-09 12:06 ` Tomas Elf
2015-10-13 11:51 ` 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=5617A8EA.8040003@intel.com \
--to=tomas.elf@intel.com \
--cc=Intel-GFX@Lists.FreeDesktop.Org \
--cc=daniel@ffwll.ch \
/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;
as well as URLs for NNTP newsgroup(s).