Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758234AbZDKScC (ORCPT ); Sat, 11 Apr 2009 14:32:02 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754721AbZDKSbx (ORCPT ); Sat, 11 Apr 2009 14:31:53 -0400 Received: from smtp1.linux-foundation.org ([140.211.169.13]:60292 "EHLO smtp1.linux-foundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754712AbZDKSbw (ORCPT ); Sat, 11 Apr 2009 14:31:52 -0400 Date: Sat, 11 Apr 2009 11:21:31 -0700 From: Andrew Morton To: Andrea Righi Cc: Stefan Richter , Krzysztof Helt , Eric Miao , LKML , Geert Uytterhoeven , "Rafael J. Wysocki" , Andrey Borzenkov , "Antonino A. Daplas" , linux-fbdev-devel@lists.sourceforge.net, linux-pm@lists.linux-foundation.org, Dave Jones , Harvey Harrison , Johannes Weiner , Pavel Roskin Subject: Re: [REGRESSION] commit 66c1ca0: {fbmem: fix fb_info->lock and mm->mmap_sem ...} causes Xfbdev not working Message-Id: <20090411112131.cc38dcf0.akpm@linux-foundation.org> In-Reply-To: <20090411150359.GA8265@linux> 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> X-Mailer: Sylpheed 2.4.8 (GTK+ 2.12.5; x86_64-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 857 Lines: 20 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? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/