Re: [PATCH] drm: Reverse lock order in pan_display_legacy()

Hi Am 11.06.19 um 15:29 schrieb Noralf Trønnes: > > > Den 11.06.2019 14.37, skrev Daniel Vetter: >> On Tue, Jun 11, 2019 at 01:57:16PM +0200, Thomas Zimmermann wrote: >>> Acquiring drm_client_dev.modeset_mutex after the locks in drm_fb_helper.dev >>> creates a deadlock with drm_setup_crtcs() as

Re: [PATCH] drm: Reverse lock order in pan_display_legacy()

Den 11.06.2019 14.37, skrev Daniel Vetter: > On Tue, Jun 11, 2019 at 01:57:16PM +0200, Thomas Zimmermann wrote: >> Acquiring drm_client_dev.modeset_mutex after the locks in drm_fb_helper.dev >> creates a deadlock with drm_setup_crtcs() as shown below: >> >> [4.959319] fbcon: radeondrmfb (fb

Re: [PATCH] drm: Reverse lock order in pan_display_legacy()

On Tue, Jun 11, 2019 at 01:57:16PM +0200, Thomas Zimmermann wrote: > Acquiring drm_client_dev.modeset_mutex after the locks in drm_fb_helper.dev > creates a deadlock with drm_setup_crtcs() as shown below: > > [4.959319] fbcon: radeondrmfb (fb0) is primary device > [4.993952] Console: s