linux-kernel - Re: [PATCH drm-misc-next v3 0/4] Fixes for vc4 hotplug rework

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <166141363051.357827.14816951155409708010.b4-ty@cerno.tech>
Date:   Thu, 25 Aug 2022 09:47:14 +0200
From:   Maxime Ripard <maxime@...no.tech>
To:     airlied@...ux.ie, daniel@...ll.ch, tzimmermann@...e.de,
        dakr@...hat.com, mripard@...nel.org
Cc:     Maxime Ripard <maxime@...no.tech>, linux-kernel@...r.kernel.org,
        dri-devel@...ts.freedesktop.org
Subject: Re: [PATCH drm-misc-next v3 0/4] Fixes for vc4 hotplug rework

On Wed, 24 Aug 2022 18:13:23 +0200, Danilo Krummrich wrote:
> I've found a few potential issues left after the hotplug rework.
> 
> In vc4_hdmi.c we're missing two mutex_unlock() calls when the device is
> unplugged.
> 
> vc4_crtc and vc4_plane seem to miss some drm_dev_enter()/drm_dev_exit() calls
> to protect against resource access after the device/driver is unbound, but the
> DRM potentially isn't freed yet and userspace can still call into the driver.
> 
> [...]

Applied to drm/drm-misc (drm-misc-next).

Thanks!
Maxime