Skip to content

panfrost: Don't double-free when handling error for unsupported GPU model

Setting the screen ro member before we checked gpu id means the error case leads to a double-free because screen->ro is set and allocated by parent who handles de-alloc a second time after we destroyed the screen we just created because ro was set.

Cc: mesa-stable

Signed-off-by: Carsten Haitzler carsten.haitzler@foss.arm.com

Edited by Carsten Haitzler

Merge request reports