From: Hans de Goede <hdegoede@redhat.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: stable@vger.kenrel.org, stable <stable@vger.kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
Dave Airlie <airlied@redhat.com>
Subject: Re: [PATCH] Revert "drm/core: Preserve the framebuffer after removing it."
Date: Fri, 20 May 2016 11:58:43 +0200 [thread overview]
Message-ID: <014fdfb5-b8a6-5c79-cabb-ab27a32d9f7b@redhat.com> (raw)
In-Reply-To: <CAKMK7uFB5uDsBBNFkgxKqwhf0j9Yqut1hHcWbgWx-y=Xn1w29w@mail.gmail.com>
Hi,
On 19-05-16 17:33, Daniel Vetter wrote:
> On Thu, May 19, 2016 at 5:15 PM, Hans de Goede <hdegoede@redhat.com> wrote:
>> This reverts commit 13803132818c ("drm/core: Preserve the framebuffer
>> after removing it.").
>>
>> This commit assumes that going through drm_framebuffer_remove() is not
>> necessary because "the fbdev code or any system compositor should restore
>> the planes anyway so there's no need to do it twice". But this is not true
>> for secondary GPUs / slave outputs.
>>
>> This revert fixes the dgpu no longer suspending on laptops with
>> switchable graphics after an external output which is connected
>> to the dgpu has been used.
>>
>> And it fixes the WARN_ON to detect drm_framebuffer leaks in
>> drm_mode_config_cleanup() triggering when unplugging an USB displaylink
>> device; or when rmmod-ing the secondary GPU kms driver on laptops with
>> switchable-graphics.
>>
>> Also this part of the reverted commit's commit-msg: "The old fb_id is
>> zero'd, so there's no danger of being able to restore the fb from fb_id."
>> is no longer true, the zero-ing does not happen until drm_framebuffer_free
>> gets called, which does not happen until the last ref is dropped, so
>> if a crtc's primary->fb is still pointing to this fb, the id will not
>> get zero'd and userspace could potentially gain access to the removed
>> fb again.
>>
>> Cc: stable@vger.kenrel.org
>> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
>
> We have a proper fix in drm-next:
>
> commit f2d580b9a8149735cbc4b59c4a8df60173658140
> Author: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> Date: Wed May 4 14:38:26 2016 +0200
>
> drm/core: Do not preserve framebuffer on rmfb, v4.
>
> That thing took forever to get merged since no one seemed to have
> cared and bothered with a tested-by. But it's on its way to stable
> kernels now.
Ah, excellent, the important thing is that this gets fixed :)
Regards,
Hans
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2016-05-20 9:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-19 15:15 [PATCH] Revert "drm/core: Preserve the framebuffer after removing it." Hans de Goede
2016-05-19 15:33 ` Daniel Vetter
2016-05-20 9:58 ` Hans de Goede [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=014fdfb5-b8a6-5c79-cabb-ab27a32d9f7b@redhat.com \
--to=hdegoede@redhat.com \
--cc=airlied@redhat.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=stable@vger.kenrel.org \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).