From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Morton Subject: Re: [REGRESSION] commit 66c1ca0: {fbmem: fix fb_info->lock and mm->mmap_sem ...} causes Xfbdev not working Date: Sat, 11 Apr 2009 11:21:31 -0700 Message-ID: <20090411112131.cc38dcf0.akpm@linux-foundation.org> References: <20090409125850.GA2727@linux> <20090410222122.87be60f6.krzysztof.h1@poczta.fm> <20090410220521.GB21294@linux> <20090411080415.7fe924a2.krzysztof.h1@poczta.fm> <49E05C36.9040204@s5r6.in-berlin.de> <20090411110840.GA7108@linux> <20090411150359.GA8265@linux> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20090411150359.GA8265@linux> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-pm-bounces@lists.linux-foundation.org Errors-To: linux-pm-bounces@lists.linux-foundation.org To: Andrea Righi Cc: Pavel Roskin , "Antonino A. Daplas" , Andrey Borzenkov , Harvey@smtp1.linux-foundation.org, Johannes Weiner , Krzysztof Helt , LKML , Stefan Richter , Geert Uytterhoeven , linux-fbdev-devel@lists.sourceforge.net, linux-pm@lists.linux-foundation.org, Harrison On Sat, 11 Apr 2009 17:04:00 +0200 Andrea Righi wrote: > fbdev: fix info->lock deadlock in fbcon_event_notify() > > fb_notifier_call_chain() is called with info->lock held, i.e. in > do_fb_ioctl() => FBIOPUT_VSCREENINFO => fb_set_var() and the some > notifier callbacks, like fbcon_event_notify(), try to re-acquire > info->lock again. > > Remove the lock/unlock_fb_info() in all the framebuffer notifier > callbacks' and be sure to always call fb_notifier_call_chain() with > info->lock held. Thanks. So do you think we should proceed with this patch instead of reverting 66c1ca0?