LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: joe.korty@ccur.com
Cc: markh@compro.net, linux-kernel@vger.kernel.org
Subject: Re: mlockall and mmap of IO devices don't mix
Date: Tue, 25 May 2004 12:47:15 -0700	[thread overview]
Message-ID: <20040525124715.5f7e61b6.akpm@osdl.org> (raw)
In-Reply-To: <20040525142728.GA10738@tsunami.ccur.com>

Joe Korty <joe.korty@ccur.com> wrote:
>
> On Fri, May 21, 2004 at 07:13:26PM -0700, Andrew Morton wrote:
>  > Mark Hounschell <markh@compro.net> wrote:
>  > >
>  > > Joe Korty wrote:
>  > > > 
>  > > > 2.6.0-test6: the use of mlockall(2) in a process that has mmap(2)ed
>  > > > the registers of an IO device will hang that process uninterruptibly.
>  > > > The task runs in an infinite loop in get_user_pages(), invoking
>  > > > follow_page() forever.
>  > > > 
>  > > > Using binary search I discovered that the problem was introduced
>  > > > in 2.5.14, specifically in ChangeSetKey
>  > > > 
>  > > >     zippel@linux-m68k.org|ChangeSet|20020503210330|37095
>  > > > 
>  > > 
>  > > I know this is an old thread but can anyone tell me if this problem is
>  > > resolved in the current 2.6.6 kernel? 
>  > > 
>  > 
>  > There's an utterly ancient patch in -mm which might fix this.
>  > 
>  > http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.6/2.6.6-mm4/broken-out/get_user_pages-handle-VM_IO.patch
> 
>  [ 2nd send -- corporate email system in the throes of being scrambled / updated ]
> 
>  Andrew,
>  I have been using this patch for ages.  Any chance of it being forwared to
>  the official tree?

That patch had its first birthday last week.  I wrote it in response to
some long-forgotten problem, failed to changelog it at the time then forgot
why I wrote it.  I kept it in the hope that I'd remember why I wrote it.  I
subsequently wrote a best-effort changelog but am unconvinced by it.  Ho
hum.

Let me genuflect a bit.  I guess we can be reasonably confident it won't
break anything.

  reply	other threads:[~2004-05-25 19:53 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-03 21:44 Joe Korty
2003-10-03 22:23 ` Andrew Morton
2003-10-03 22:55   ` Joe Korty
2003-10-03 23:06     ` Andrew Morton
2003-10-03 23:28       ` Joe Korty
2003-10-03 23:15     ` Andrew Morton
2003-10-03 23:54       ` Joe Korty
2003-10-04  0:27         ` Andrew Morton
2003-10-04  5:47           ` David S. Miller
2003-10-04  9:29             ` Ingo Oeser
2004-05-21 11:34 ` Mark Hounschell
2004-05-22  2:13   ` Andrew Morton
2004-05-22 10:47     ` Mark Hounschell
2004-05-23 12:58       ` Mark Hounschell
2004-05-25 14:27     ` Joe Korty
2004-05-25 19:47       ` Andrew Morton [this message]
2004-05-25 21:31         ` Joe Korty
2004-07-16 21:01         ` Mark Hounschell
     [not found] <CFYv.787.23@gated-at.bofh.it>
2003-10-04  7:02 ` Andi Kleen
2003-10-04  7:42   ` Andrew Morton
2003-10-04  8:29     ` Andi Kleen
2003-10-04  8:47   ` Ingo Oeser
2003-10-04  9:17     ` Andi Kleen
2003-10-04  9:22       ` Russell King
2003-10-04 10:02         ` Ingo Oeser
2003-10-04 10:13           ` Russell King
2003-10-04 14:19             ` Ingo Oeser
2003-10-04 14:32           ` Martin J. Bligh

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=20040525124715.5f7e61b6.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=joe.korty@ccur.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markh@compro.net \
    --subject='Re: mlockall and mmap of IO devices don'\''t mix' \
    /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

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).