From: Andi Kleen <ak@muc.de>
To: Joe Korty <joe.korty@ccur.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: mlockall and mmap of IO devices don't mix
Date: Sat, 04 Oct 2003 09:02:59 +0200 [thread overview]
Message-ID: <m34qyp7ae4.fsf@averell.firstfloor.org> (raw)
In-Reply-To: <CFYv.787.23@gated-at.bofh.it> (Joe Korty's message of "Fri, 03 Oct 2003 23:50:19 +0200")
Joe Korty <joe.korty@ccur.com> writes:
>
> I do not believe that the above constitutes a correct fix. The
> problem is that follow_pages() is fundamentally not able to handle a
> mapping which does not have a 'struct page' backing it up, and a
> mapping to IO memory by definition has no 'struct page' structure to
> back it up.
The 2.4 vm scanner handles this by always checking VALID_PAGE().
Maybe follow_pages() should do that too?
-Andi
next parent reply other threads:[~2003-10-04 7:03 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CFYv.787.23@gated-at.bofh.it>
2003-10-04 7:02 ` Andi Kleen [this message]
2003-10-04 7:42 ` mlockall and mmap of IO devices don't mix 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:19 ` Ingo Oeser
2003-10-04 14:32 ` Martin J. Bligh
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
2004-05-25 21:31 ` Joe Korty
2004-07-16 21:01 ` Mark Hounschell
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=m34qyp7ae4.fsf@averell.firstfloor.org \
--to=ak@muc.de \
--cc=joe.korty@ccur.com \
--cc=linux-kernel@vger.kernel.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 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.