[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <00117d58-2a47-4e2b-225b-952e0e98df2f@redhat.com>
Date: Fri, 6 May 2022 15:18:44 +0200
From: Javier Martinez Canillas <javierm@...hat.com>
To: Andrzej Hajda <andrzej.hajda@...el.com>,
linux-kernel@...r.kernel.org
Cc: linux-fbdev@...r.kernel.org,
Daniel Vetter <daniel.vetter@...ll.ch>,
Helge Deller <deller@....de>, dri-devel@...ts.freedesktop.org,
Peter Jones <pjones@...hat.com>,
Thomas Zimmermann <tzimmermann@...e.de>
Subject: Re: [PATCH v3 3/4] fbdev: efifb: Cleanup fb_info in .fb_destroy
rather than .remove
Hello Andrzej,
On 5/6/22 15:07, Andrzej Hajda wrote:
> On 06.05.2022 00:05, Javier Martinez Canillas wrote:
[snip]
>> +
>> + framebuffer_release(info);
>> +
>> if (request_mem_succeeded)
>> release_mem_region(info->apertures->ranges[0].base,
>> info->apertures->ranges[0].size);
>
> You are releasing info, then you are using it.
>
> I suspect it is responsible for multiple failures of Intel CI [1].
>
Yes, it is :( sorry about the mess. Ville already reported this to me.
I'll post a patch in a minute.
I wonder how this didn't happen before since .remove() happens before
.fb_destroy() AFAIU...
--
Best regards,
Javier Martinez Canillas
Linux Engineering
Red Hat
Powered by blists - more mailing lists