[Top] [All Lists]

Re: [BUG] drivers/video/sis: deadlock introduced by "fbdev: add mutex fo

To: Paul Mundt <>
Subject: Re: [BUG] drivers/video/sis: deadlock introduced by "fbdev: add mutex for fb_mmap locking"
From: Linus Torvalds <>
Date: Sun, 5 Jul 2009 08:19:40 -0700 (PDT)
Cc: Wu Zhangjin <>,,,, Krzysztof Helt <>, Peter Zijlstra <>, "Rafael J. Wysocki" <>, Andrew Morton <>, Ralf Baechle <>, ???? <>, zhangfx <>
In-reply-to: <>
Original-recipient: rfc822;
References: <1246785112.14240.34.camel@falcon> <alpine.LFD.2.01.0907050715490.3210@localhost.localdomain> <> <alpine.LFD.2.01.0907050756280.3210@localhost.localdomain> <>
User-agent: Alpine 2.01 (LFD 1184 2008-12-16)

On Mon, 6 Jul 2009, Paul Mundt wrote:
> >
> > Why not "lock" as well?
> I had that initially, but matroxfb will break if we do that, and
> presently nothing cares about trying to take ->lock that early on.

I really would rather have consistency than some odd rules like that.

In particular - if matroxfb is different and needs its own lock 
initialization because it doesn't use the common allocation routine, then 
please make _that_ consistent too. Rather than have it special-case just 
one lock that it needs to initialize separately, make it clear that since 
it does its own allocations it needs to initialize _everything_ 

Otherwise anybody grepping for things will always be confused, since 
depending on random factors they'll notice the initializations in one 
place or the other, and then do the wrong thing - exactly like mm_lock was 
not correctly initialized this time around.

In other words: it's actually _better_ to make the matroxfb pain _more_ 
obvious rather than less.

And maybe we can deprecate the driver, throw it out entirely, or have 
somebody actually fix it?


<Prev in Thread] Current Thread [Next in Thread>