From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 96596C433EF for ; Fri, 17 Jun 2022 06:46:35 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1380337AbiFQGqd (ORCPT ); Fri, 17 Jun 2022 02:46:33 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56100 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1380318AbiFQGq1 (ORCPT ); Fri, 17 Jun 2022 02:46:27 -0400 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 457F124962 for ; Thu, 16 Jun 2022 23:46:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1655448384; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=+hQ4DbL4FBpOEp/E50yBIWWCZyfpTsZUOXGgMRiUx5A=; b=G1/pTfJy2OCbNrOSW32zfzuZAFdZaPiOsJXyl2USrFCmRbPY1pXGP+P9GxIqXw6RkYByLN zK+B2tY5FTOfwBmrSoYilg6NADCHv57rNWM/cT5r08jKhHTKWsugtC7FYt/Pak7tFBfv60 pfZrnXS5U4ynkaxus3uyZ4vU1Jyf9Ns= Received: from mail-wm1-f70.google.com (mail-wm1-f70.google.com [209.85.128.70]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-306-X5Tyf6aVNA6fgLtD0ypjaA-1; Fri, 17 Jun 2022 02:46:22 -0400 X-MC-Unique: X5Tyf6aVNA6fgLtD0ypjaA-1 Received: by mail-wm1-f70.google.com with SMTP id j31-20020a05600c1c1f00b0039c481c4664so1265789wms.7 for ; Thu, 16 Jun 2022 23:46:22 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:cc:references:from:in-reply-to :content-transfer-encoding; bh=+hQ4DbL4FBpOEp/E50yBIWWCZyfpTsZUOXGgMRiUx5A=; b=IB2tz9xGwINVln8E0/GDMyQoldKqxgl0Drq640G7YDQX+Z6v+5Y+hTUCsYbeg5bdKi B8/P5B1++VYdSz7A2vAVV/VcW4l6mmGhRU7LjlkWKP4dDJgkYZ0Fr5VwFDgn1BvmPIX6 zD141jxrwL5ge1N3k3Yyt0q630yygxtuGynnBwXJzErq558AeXzaQOVGU4bGwm+rtCJd aTjmTvWWdQZNF/hqWoANycyALoexRXDn5SzYmbs4M9JoKuYe4YBvbIwcZ9GTZ8d2CIrZ eOq8qZARQ4DUkkXT0UktYcU03LHsbljCQAYpsQFBHl8px4+1zXat67FJ6hDp10n8npcz aakA== X-Gm-Message-State: AJIora9WrSkZJLltb1c5J4amZLxwOhqq8MkLMS/paDy0zMsQvJbUOwkd fW2xGWXyXlN++1umBR26NPMvsuyazYZQKzsh4JywYmHUmCGf/AMHCH8Q2GIwX2RP5zo2luum8AJ XZhbvYL3AL0kJ6J4l5qIJmGTv X-Received: by 2002:a05:600c:3489:b0:39d:b58f:6797 with SMTP id a9-20020a05600c348900b0039db58f6797mr8604231wmq.205.1655448381561; Thu, 16 Jun 2022 23:46:21 -0700 (PDT) X-Google-Smtp-Source: AGRyM1sQ/maUwRNsLJ+dTUUPQVEZ65LnPBk/IMQjAM9szqh0Rf1kxBOzJQNiJ8h903v4iEFev4ehFw== X-Received: by 2002:a05:600c:3489:b0:39d:b58f:6797 with SMTP id a9-20020a05600c348900b0039db58f6797mr8604207wmq.205.1655448381308; Thu, 16 Jun 2022 23:46:21 -0700 (PDT) Received: from [192.168.1.129] (205.pool92-176-231.dynamic.orange.es. [92.176.231.205]) by smtp.gmail.com with ESMTPSA id f11-20020a05600c4e8b00b003973a3fe4fasm4787183wmq.42.2022.06.16.23.46.19 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 16 Jun 2022 23:46:20 -0700 (PDT) Message-ID: Date: Fri, 17 Jun 2022 08:46:18 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.10.0 Subject: Re: [PATCH v6 3/5] fbdev: Disable sysfb device registration when removing conflicting FBs Content-Language: en-US To: Zack Rusin , "linux-kernel@vger.kernel.org" Cc: "linux-fbdev@vger.kernel.org" , "kraxel@redhat.com" , "tzimmermann@suse.de" , "gregkh@linuxfoundation.org" , "alex.williamson@redhat.com" , "dri-devel@lists.freedesktop.org" , "daniel.vetter@ffwll.ch" , "lersek@redhat.com" , "kvm@vger.kernel.org" , "deller@gmx.de" , Linux-graphics-maintainer References: <20220607182338.344270-1-javierm@redhat.com> <20220607182338.344270-4-javierm@redhat.com> <38473dcd-0666-67b9-28bd-afa2d0ce434a@redhat.com> <603e3613b9b8ff7815b63f294510d417b5b12937.camel@vmware.com> <97565fb5-cf7f-5991-6fb3-db96fe239ee8@redhat.com> <711c88299ef41afd8556132b7c1dcb75ee7e6117.camel@vmware.com> From: Javier Martinez Canillas In-Reply-To: <711c88299ef41afd8556132b7c1dcb75ee7e6117.camel@vmware.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello Zack, On 6/17/22 03:35, Zack Rusin wrote: > On Fri, 2022-06-17 at 01:21 +0200, Javier Martinez Canillas wrote: >> 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. > > Sounds good. Let me know if you'd like me to try it without SIMPLEFB. > Yes, please do. Either with CONFIG_SYSFB_SIMPLEFB disabled and CONFIG_FB_EFI enabled (so that "efi-framebuffer" is registered and efifb probed) or with CONFIG_SYSFB_SIMPLEFB but CONFIG_FB_SIMPLE enabled (so "simple-framebuffer is used too but with simplefb instead of simpledrm). I'm not able to reproduce, it would be useful to have another data point. -- Best regards, Javier Martinez Canillas Linux Engineering Red Hat