From: Dave Airlie Date: Thu, 17 Aug 2017 01:08:46 +0000 (+0100) Subject: radv: don't crash if we have no framebuffer X-Git-Tag: upstream/18.1.0~6502 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=4a091b0788664f73bbb35c14d04c00cebf37e17a;p=platform%2Fupstream%2Fmesa.git radv: don't crash if we have no framebuffer Recording secondaries with no framebuffer attachment may make this happen, though this might not be the complete solution. (esp if someone does meta stuff in there, would we have to save things, not sure). Fixes: f4e499ec791 ("radv: add initial non-conformant radv vulkan driver") Reviewed-by: Bas Nieuwenhuizen Signed-off-by: Dave Airlie --- diff --git a/src/amd/vulkan/radv_cmd_buffer.c b/src/amd/vulkan/radv_cmd_buffer.c index cbe0de1..fe8f3f2 100644 --- a/src/amd/vulkan/radv_cmd_buffer.c +++ b/src/amd/vulkan/radv_cmd_buffer.c @@ -1212,6 +1212,10 @@ radv_emit_framebuffer_state(struct radv_cmd_buffer *cmd_buffer) struct radv_framebuffer *framebuffer = cmd_buffer->state.framebuffer; const struct radv_subpass *subpass = cmd_buffer->state.subpass; + /* this may happen for inherited secondary recording */ + if (!framebuffer) + return; + for (i = 0; i < 8; ++i) { if (i >= subpass->color_count || subpass->color_attachments[i].attachment == VK_ATTACHMENT_UNUSED) { radeon_set_context_reg(cmd_buffer->cs, R_028C70_CB_COLOR0_INFO + i * 0x3C,