Re: [PATCH] drm: Fix possible deadlock in drm_mode_config_cleanup()

2017-12-15 Thread kbuild test robot
Hi Marek, I love your patch! Perhaps something to improve: [auto build test WARNING on v4.15-rc3] [cannot apply to drm/drm-next drm-exynos/exynos-drm/for-next drm-intel/for-linux-next next-20171215] [if your patch is applied to the wrong git tree, please drop us a note to help improve the syste

Re: [PATCH] drm: Fix possible deadlock in drm_mode_config_cleanup()

2017-12-13 Thread Daniel Vetter
On Wed, Dec 13, 2017 at 09:57:20AM +0100, Marek Szyprowski wrote: > drm_mode_config_cleanup() might be called from a workqueue context (for > example in error path handling of deferred probe), so it must not call > flush_scheduled_work(), because it would deadlock in such case. Replace > that call

Re: [PATCH] drm: Fix possible deadlock in drm_mode_config_cleanup()

2017-12-13 Thread Chris Wilson
Quoting Marek Szyprowski (2017-12-13 08:57:20) > drm_mode_config_cleanup() might be called from a workqueue context (for > example in error path handling of deferred probe), so it must not call > flush_scheduled_work(), because it would deadlock in such case. Replace > that call with explicit count

[PATCH] drm: Fix possible deadlock in drm_mode_config_cleanup()

2017-12-13 Thread Marek Szyprowski
drm_mode_config_cleanup() might be called from a workqueue context (for example in error path handling of deferred probe), so it must not call flush_scheduled_work(), because it would deadlock in such case. Replace that call with explicit counting of the scheduled connector free works and waiting u