[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <97565fb5-cf7f-5991-6fb3-db96fe239ee8@redhat.com>
Date: Fri, 17 Jun 2022 01:21:18 +0200
From: Javier Martinez Canillas <javierm@...hat.com>
To: Zack Rusin <zackr@...are.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Cc: "linux-fbdev@...r.kernel.org" <linux-fbdev@...r.kernel.org>,
"kraxel@...hat.com" <kraxel@...hat.com>,
"tzimmermann@...e.de" <tzimmermann@...e.de>,
"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
"alex.williamson@...hat.com" <alex.williamson@...hat.com>,
"dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>,
"daniel.vetter@...ll.ch" <daniel.vetter@...ll.ch>,
"lersek@...hat.com" <lersek@...hat.com>,
"kvm@...r.kernel.org" <kvm@...r.kernel.org>,
"deller@....de" <deller@....de>,
Linux-graphics-maintainer <Linux-graphics-maintainer@...are.com>
Subject: Re: [PATCH v6 3/5] fbdev: Disable sysfb device registration when
removing conflicting FBs
On 6/17/22 00:18, Javier Martinez Canillas wrote:
> On 6/16/22 23:03, Zack Rusin wrote:
[snip]
>
> I'll look at this tomorrow but in the meantime, could you please look if the following
> commits on top of drm-misc-next help ?
>
> d258d00fb9c7 fbdev: efifb: Cleanup fb_info in .fb_destroy rather than .remove
> 1b5853dfab7f fbdev: efifb: Fix a use-after-free due early fb_info cleanup
>
Scratch that. I see in your config now that you are not using efifb but instead
simpledrm: CONFIG_DRM_SIMPLEDRM=y, CONFIG_SYSFB_SIMPLEFB=y and CONFIG_DRM_VMWGFX.
Since you mentioned efifb I misunderstood that you are using it. Anyways, as
said I'll investigate this tomorrow.
--
Best regards,
Javier Martinez Canillas
Linux Engineering
Red Hat
Powered by blists - more mailing lists