> Could the error handling path be updated to ensure the buffer is properly > destroyed when this occurs?
Thanks for pointing this out. This appears to be a pre-existing issue and is not introduced by this patch. The purpose of the current patch is limited to preventing the restore callback from dereferencing a partially initialized fbdev client. The cleanup concern looks valid. I will inspect the buffer ownership and error-unwind paths around register_framebuffer() failure. If additional cleanup is required, I will handle it separately so that the restore fix remains focused. Thanks, Chenglong She
