linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
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, Andrew Morton <akpm@linux-foundation.org>,
	Ingo Molnar <mingo@elte.hu>,
	righi.andrea@gmail.com
Subject: Re: [PATCH] add mutex to fbdev for fb_mmap locking
Date: Tue, 2 Jun 2009 11:56:41 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LFD.2.01.0906021154270.3351@localhost.localdomain> (raw)
In-Reply-To: <20090602195240.0af2f21c@lxorguk.ukuu.org.uk>



On Tue, 2 Jun 2009, Alan Cox wrote:
>
> > ie the fact that the TTY layer does user-mode copies while holding some 
> > tty lock. So now the tty layer introduces that chain from some random lock 
> > to the mmap_sem.
> 
> Its basically holding the termios lock to copy from the struct termios to
> user space which means its trivial to do copy to a stack buffer first. I
> can fix that pretty easily if you want.

It would be good. I don't know if it matters for any other path, but 
mmap_sem has always been a total _bitch_ to work around for deadlocks, so 
it's always good to try to avoid holding another lock while doing copying 
to/from user. 

I thought we already always copied things to a buffer (for conversion 
reasons, ie doing the whole "ktermios<->random-user-termios-of-the-day" 
thing), but I guess I was wrong.

		Linus

------------------------------------------------------------------------------
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-02 18:57 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
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 [this message]
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=alpine.LFD.2.01.0906021154270.3351@localhost.localdomain \
    --to=torvalds@linux-foundation.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=geert@linux-m68k.org \
    --cc=krzysztof.h1@wp.pl \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=mingo@elte.hu \
    --cc=righi.andrea@gmail.com \
    /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).