linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: krzysztof.h1@wp.pl,
	Linux-fbdev-devel <linux-fbdev-devel@lists.sourceforge.net>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	geert@linux-m68k.org, akpm@linux-foundation.org,
	righi.andrea@gmail.com
Subject: Re: [PATCH] add mutex to fbdev for fb_mmap locking
Date: Mon, 1 Jun 2009 22:45:51 +0200	[thread overview]
Message-ID: <20090601204551.GA2702@elte.hu> (raw)
In-Reply-To: <alpine.LFD.2.01.0906011329400.3435@localhost.localdomain>


* Linus Torvalds <torvalds@linux-foundation.org> wrote:

> On Mon, 1 Jun 2009, Krzysztof Helt wrote:
> > 
> > I will fix it.
> 
> Thanks.
> 
> > If the revert to BKL is rejected this patch may wait till 
> > 2.6.31.
> 
> Ahh, so this one helps clean up locking, but doesn't fix any 
> actual regressions? I was going to ask you about that.
> 
> Btw - one thing you could try on the whole lockdep front - and I 
> realize that this is a _total_ hack - is to try the patch below.

One thing that might be less obscure is to add:

	lockdep_off();
	...
	lockdep_on();

to around those user-copies.

Those cause lockdep to totally ignore those dependencies. It's an 
ugly hack - but at least a readable hack IMO. With big red warning 
signs, a promise to fix this ASAP, etc.

It's still much better than a big ugly revert back to the BKL (of 
course - and regardless of how late we are in the cycle) - and 
probably a bit better than the atomic-copy hack.

Or am i missing something?

	Ingo

------------------------------------------------------------------------------
OpenSolaris 2009.06 is a cutting edge operating system for enterprises 
looking to deploy the next generation of Solaris that includes the latest 
innovations from Sun and the OpenSource community. Download a copy and 
enjoy capabilities such as Networking, Storage and Virtualization. 
Go to: http://p.sf.net/sfu/opensolaris-get

  reply	other threads:[~2009-06-01 20:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200905282134.n4SLYNwv027999@imap1.linux-foundation.org>
     [not found] ` <alpine.LFD.2.01.0905290820510.3435@localhost.localdomain>
     [not found]   ` <20090530121128.5f04179d.krzysztof.h1@poczta.fm>
     [not found]     ` <alpine.LFD.2.01.0905300805350.3435@localhost.localdomain>
2009-05-31 14:24       ` [PATCH] add mutex to fbdev for fb_mmap locking Krzysztof Helt
2009-05-31 17:09         ` Linus Torvalds
2009-06-01 20:24           ` Krzysztof Helt
2009-06-01 20:38             ` Linus Torvalds
2009-06-01 20:45               ` Ingo Molnar [this message]
2009-06-02 15:09               ` Krzysztof Helt
2009-06-02 18:06               ` Krzysztof Helt
2009-06-02 18:13                 ` Linus Torvalds
2009-06-02 18:52                   ` Alan Cox
2009-06-02 18:56                     ` Linus Torvalds
2009-06-02 19:11                       ` Linus Torvalds
2009-06-02 19:36                         ` Alan Cox
2009-06-02 19:51                           ` Linus Torvalds

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=20090601204551.GA2702@elte.hu \
    --to=mingo@elte.hu \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=geert@linux-m68k.org \
    --cc=krzysztof.h1@wp.pl \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=righi.andrea@gmail.com \
    --cc=torvalds@linux-foundation.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).