public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: "David S. Miller" <davem@davemloft.net>
Cc: linux-kernel@vger.kernel.org, Andrea Arcangeli <andrea@novell.com>
Subject: Re: loops in get_user_pages() for VM_IO
Date: Tue, 16 Nov 2004 22:33:38 -0800	[thread overview]
Message-ID: <20041116223338.08bb6701.akpm@osdl.org> (raw)
In-Reply-To: <20041116180718.2fa35fbb.davem@davemloft.net>

"David S. Miller" <davem@davemloft.net> wrote:
>
> In any event, it is still an open question whether get_user_pages()
>  and thus make_pages_present() is meant to be able to handle
>  VM_IO areas.

It doesn't make a lot of sense.  Andrea says that the only caller of
get_user_pages() which uses a null `pages' arg is mlock(), and mlock of a
VM_IO region is currently causing hangs, and proposes this change:


--- sles/mm/memory.c.~1~	2004-11-12 12:30:25.000000000 +0100
+++ sles/mm/memory.c	2004-11-16 17:58:02.752131952 +0100
@@ -753,7 +753,7 @@ int get_user_pages(struct task_struct *t
 			continue;
 		}
 
-		if (!vma || (pages && (vma->vm_flags & VM_IO))
+		if (!vma || (vma->vm_flags & VM_IO)
 				|| !(flags & vma->vm_flags))
 			return i ? : -EFAULT;

which should fix up the sbuslib.c problem.

Although I suspect this change will make mlockall() return -EFAULT or a
short result to userspace if the caller had a VM_IO region mapped, which
doesn't seem appropriate.  So perhaps we should silently bale out in the
VM_IO case.

Or, better, simply advance over the VM_IO vma and onto the next one?


--- 25/mm/memory.c~get_user_pages-skip-VM_IO	2004-11-16 22:24:34.470017896 -0800
+++ 25-akpm/mm/memory.c	2004-11-16 22:32:04.890543568 -0800
@@ -761,9 +761,27 @@ int get_user_pages(struct task_struct *t
 			continue;
 		}
 
-		if (!vma || (pages && (vma->vm_flags & VM_IO))
-				|| !(flags & vma->vm_flags))
-			return i ? : -EFAULT;
+		if (!vma || !(flags & vma->vm_flags))
+			return i ? i : -EFAULT;
+
+		if (vma->vm_flags & VM_IO) {
+			if (pages) {
+				/*
+				 * No, you cannot gather pageframes from VM_IO
+				 * regions
+				 */
+				return i ? i : -EFAULT;
+			}
+			/*
+			 * OK, someone is simply trying to fault in some pages
+			 * and they encountered a VM_IO region.  mlockall()
+			 * can do this.  Simply skip the vma
+			 */
+			start = vma->vm_end;
+			len -= (vma->vm_end - vma->vm_start) >> PAGE_SHIFT;
+			i += (vma->vm_end - vma->vm_start) >> PAGE_SHIFT;
+			continue;
+		}
 
 		if (is_vm_hugetlb_page(vma)) {
 			i = follow_hugetlb_page(mm, vma, pages, vmas,
_

(I've probably screwed something up there.)

  reply	other threads:[~2004-11-17  6:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-17  1:53 loops in get_user_pages() for VM_IO David S. Miller
2004-11-17  2:07 ` David S. Miller
2004-11-17  6:33   ` Andrew Morton [this message]
2004-11-17  6:26     ` David S. Miller
2004-11-17 13:44     ` Andrea Arcangeli
2004-11-17 16:40       ` Andrea Arcangeli
2004-11-17 19:37         ` Hugh Dickins
2004-11-18 19:52           ` [PATCH] " Hugh Dickins

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=20041116223338.08bb6701.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=andrea@novell.com \
    --cc=davem@davemloft.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox