All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrea Righi <righi.andrea@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Stefan Richter <stefanr@s5r6.in-berlin.de>,
	Krzysztof Helt <krzysztof.h1@poczta.fm>,
	Eric Miao <eric.y.miao@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	Andrey Borzenkov <arvidjaar@gmail.com>,
	"Antonino A. Daplas" <adaplas@gmail.com>,
	linux-fbdev-devel@lists.sourceforge.net,
	linux-pm@lists.linux-foundation.org,
	Dave Jones <davej@redhat.com>,
	Harvey Harrison <harvey.harrison@gmail.com>,
	Johannes Weiner <hannes@cmpxchg.org>,
	Pavel Roskin <proski@gnu.org>
Subject: Re: [REGRESSION] commit 66c1ca0: {fbmem: fix fb_info->lock and mm->mmap_sem ...} causes Xfbdev not working
Date: Sat, 11 Apr 2009 21:32:26 +0200	[thread overview]
Message-ID: <20090411193226.GA5440@linux> (raw)
In-Reply-To: <20090411112131.cc38dcf0.akpm@linux-foundation.org>

On Sat, Apr 11, 2009 at 11:21:31AM -0700, Andrew Morton wrote:
> On Sat, 11 Apr 2009 17:04:00 +0200 Andrea Righi <righi.andrea@gmail.com> 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?

Yes, there's no need to revert 66c1ca0 now, otherwise we'll simply
reintroduce the info->lock / mm->mmap_sem circular locking dependency.

I'd like to test the fbdev mode switching, but it seems intelfb doesn't
support it with LVDS ports (and at the moment I've not a CRT here...).

Anyway, if someone will have troubles with mode switching I'm quite sure
we can fix it on top of this patch.

-Andrea

  reply	other threads:[~2009-04-11 19:32 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-09 11:36 [REGRESSION] commit 66c1ca0: {fbmem: fix fb_info->lock and mm->mmap_sem ...} causes Xfbdev not working Eric Miao
2009-04-09 12:58 ` Andrea Righi
2009-04-09 12:58 ` Andrea Righi
2009-04-10 20:21   ` Krzysztof Helt
2009-04-10 20:21   ` Krzysztof Helt
2009-04-10 21:16     ` Andrew Morton
2009-04-10 21:16       ` Andrew Morton
2009-04-10 22:05     ` Andrea Righi
2009-04-11  6:04       ` Krzysztof Helt
2009-04-11  6:04       ` Krzysztof Helt
2009-04-11  9:00         ` Stefan Richter
2009-04-11  9:00         ` Stefan Richter
2009-04-11 11:08           ` Andrea Righi
2009-04-11 11:08           ` Andrea Righi
2009-04-11 15:04             ` Andrea Righi
2009-04-11 15:04             ` Andrea Righi
2009-04-11 18:21               ` Andrew Morton
2009-04-11 18:21                 ` Andrew Morton
2009-04-11 19:32                 ` Andrea Righi [this message]
2009-04-11 19:32                 ` Andrea Righi
2009-04-13 23:34               ` Andreas Schwab
2009-04-13 23:34               ` Andreas Schwab
2009-04-17 16:25               ` Krzysztof Helt
     [not found]               ` <20090417182507.0bd85ccc.krzysztof.h1@poczta.fm>
2009-04-17 22:51                 ` Andrea Righi
2009-04-17 22:51                 ` Andrea Righi
2009-04-11 15:04             ` Andrea Righi
2009-04-10 22:05     ` Andrea Righi
2009-04-10 17:40 ` Krzysztof Helt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090411193226.GA5440@linux \
    --to=righi.andrea@gmail.com \
    --cc=adaplas@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=arvidjaar@gmail.com \
    --cc=davej@redhat.com \
    --cc=eric.y.miao@gmail.com \
    --cc=geert@linux-m68k.org \
    --cc=hannes@cmpxchg.org \
    --cc=harvey.harrison@gmail.com \
    --cc=krzysztof.h1@poczta.fm \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=proski@gnu.org \
    --cc=rjw@sisk.pl \
    --cc=stefanr@s5r6.in-berlin.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.