From: Erik Faye-Lund Date: Wed, 6 Mar 2019 12:29:35 +0000 (+0100) Subject: gallium/u_vbuf: support NULL-resources X-Git-Tag: upstream/19.3.0~6855 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=a8e8204b18697e8f45643abdd5b32b6c8f3659ac;p=platform%2Fupstream%2Fmesa.git gallium/u_vbuf: support NULL-resources It's legal for a buffer-object to have a NULL-resource, but let's just skip over it, as there's nothing to do. Signed-off-by: Erik Faye-Lund Reviewed-by: Marek Olšák --- diff --git a/src/gallium/auxiliary/util/u_vbuf.c b/src/gallium/auxiliary/util/u_vbuf.c index 02a59bc..200bfff 100644 --- a/src/gallium/auxiliary/util/u_vbuf.c +++ b/src/gallium/auxiliary/util/u_vbuf.c @@ -418,6 +418,9 @@ u_vbuf_translate_buffers(struct u_vbuf *mgr, struct translate_key *key, unsigned size = vb->stride ? num_vertices * vb->stride : sizeof(double)*4; + if (!vb->buffer.resource) + continue; + if (offset + size > vb->buffer.resource->width0) { /* Don't try to map past end of buffer. This often happens when * we're translating an attribute that's at offset > 0 from the