Re: [Intel-gfx] [PATCH] drm/i915: Explosion following OOM in do_execbuffer.

On Fri, 2 Jul 2010 08:57:15 +0100, Chris Wilson wrote: > Oops, when merging the extra details following an OOM, I missed that > driver_private is now NULL and the correct way to convert from the > drm_gem_object into the drm_i915_gem_object is to use to_intel_bo(). Applied. Thanks! pgp5GAjQT

[Intel-gfx] [PATCH] drm/i915: Explosion following OOM in do_execbuffer.

Oops, when merging the extra details following an OOM, I missed that driver_private is now NULL and the correct way to convert from the drm_gem_object into the drm_i915_gem_object is to use to_intel_bo(). BUG: unable to handle kernel NULL pointer dereference at 0069 IP: [] i915_gem_do_execbuff

Re: [Intel-gfx] [PATCH] drm/i915: Explosion following OOM in do_execbuffer.

On Wed, 9 Jun 2010 17:04:24 +0100, Chris Wilson wrote: > Oops, when merging the extra details following an OOM, I missed that > driver_private is now NULL and the correct way to convert from the > drm_gem_object into the drm_i915_gem_object is to use to_intel_bo(). > > BUG: unable to handle ker

[Intel-gfx] [PATCH] drm/i915: Explosion following OOM in do_execbuffer.

Oops, when merging the extra details following an OOM, I missed that driver_private is now NULL and the correct way to convert from the drm_gem_object into the drm_i915_gem_object is to use to_intel_bo(). BUG: unable to handle kernel NULL pointer dereference at 0069 IP: [] i915_gem_do_execbuff