From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter =?iso-8859-1?q?H=FCwe?= Subject: Re: [PATCH 1/2] drm/nouveau: Add lock on drm_helper_resume_force_mode Date: Sat, 14 Apr 2012 02:59:32 +0200 Message-ID: <201204140259.33243.PeterHuewe@gmx.de> References: <1334362145-27627-1-git-send-email-peterhuewe@gmx.de> <20120414005219.GG13995@burratino> Mime-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20120414005219.GG13995@burratino> Sender: linux-kernel-owner@vger.kernel.org To: Jonathan Nieder Cc: David Airlie , Ben Skeggs , Maxim Levitsky , Dave Airlie , Alex Deucher , Jerome Glisse , Christian =?iso-8859-1?q?K=F6nig?= , Michel =?iso-8859-1?q?D=E4nzer?= , dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org, stable@vger.kernel.org, stable@kernel.org List-Id: dri-devel@lists.freedesktop.org Am Samstag 14 April 2012, 02:52:19 schrieb Jonathan Nieder: > Hi, > > Peter Huewe wrote: > > mode_config should be locked when calling drm_helper_resume_force_mode. > > This patch adds the lock, similar to #927a2f119. > > Does this fix a problem that has been observed in the wild, or only a > theoretical one? > > Curious, > Jonathan Only theoretical ;) Since all other drivers always lock around drm_helper_resume_force_mode I guessed this is good practice. And since problem area is quite similar to the one mentioned in #927a2f119 / 234f78a683e http://git.kernel.org/?p=linux/kernel/git/stable/linux- stable.git;a=commit;h=234f78a683e30d6d4628846fde4a822c0e385529 the bug might happen in the wild. Thanks, Peter