From: Carsten Otte <cotte@de.ibm.com>
To: Hugh Dickins <hugh@veritas.com>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>,
Linux Memory Management <linux-mm@kvack.org>
Subject: [RFC] [patch] mm: fix xip issue with /dev/zero
Date: Mon, 26 Feb 2007 19:04:10 +0100 [thread overview]
Message-ID: <1172513050.5685.21.camel@cotte.boeblingen.de.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0702181855230.16343@blonde.wat.veritas.com>
Thanks for your review feedback Hugh, I do appreciate it. Here comes my
second attempt:
This patch fixes the bug, that reading into xip mapping from /dev/zero
fills the user page table with ZERO_PAGE() entries. Later on, xip cannot
tell which pages have been ZERO_PAGE() filled by access to a sparse
mapping, and which ones origin from /dev/zero. It will unmap ZERO_PAGE
from all mappings when filling the sparse hole with data.
xip does now use its own zeroed page for its sparse mappings.
Signed-off-by: Carsten Otte <cotte@de.ibm.com>
---
diff -pruN linux-2.6/mm/filemap_xip.c linux-2.6+fix/mm/filemap_xip.c
--- linux-2.6/mm/filemap_xip.c 2007-02-26 13:46:28.000000000 +0100
+++ linux-2.6+fix/mm/filemap_xip.c 2007-02-26 18:45:15.000000000 +0100
@@ -17,6 +17,31 @@
#include "filemap.h"
/*
+ * We do use our own empty page to avoid interference with other users
+ * of ZERO_PAGE(), such as /dev/zero
+ */
+static struct page *__xip_sparse_page = NULL;
+static DEFINE_SPINLOCK(xip_alloc_lock);
+
+static struct page *xip_sparse_page(void)
+{
+ unsigned long tmp;
+
+ if (!__xip_sparse_page) {
+ tmp = get_zeroed_page(GFP_ATOMIC);
+ if (!tmp)
+ return NULL;
+ spin_lock(&xip_alloc_lock);
+ if (!__xip_sparse_page)
+ __xip_sparse_page = virt_to_page(tmp);
+ else
+ free_page (tmp);
+ spin_unlock(&xip_alloc_lock);
+ }
+ return __xip_sparse_page;
+}
+
+/*
* This is a file read routine for execute in place files, and uses
* the mapping->a_ops->get_xip_page() function for the actual low-level
* stuff.
@@ -63,12 +88,18 @@ do_xip_mapping_read(struct address_space
page = mapping->a_ops->get_xip_page(mapping,
index*(PAGE_SIZE/512), 0);
- if (!page)
+ if (!page) {
+ desc->error = -EIO;
goto no_xip_page;
+ }
if (unlikely(IS_ERR(page))) {
if (PTR_ERR(page) == -ENODATA) {
/* sparse */
- page = ZERO_PAGE(0);
+ page = xip_sparse_page();
+ if (!page) {
+ desc->error = -ENOMEM;
+ goto no_xip_page;
+ }
} else {
desc->error = PTR_ERR(page);
goto out;
@@ -102,7 +133,6 @@ do_xip_mapping_read(struct address_space
no_xip_page:
/* Did not get the page. Report it */
- desc->error = -EIO;
goto out;
}
@@ -162,7 +192,7 @@ EXPORT_SYMBOL_GPL(xip_file_sendfile);
* xip_write
*
* This function walks all vmas of the address_space and unmaps the
- * ZERO_PAGE when found at pgoff. Should it go in rmap.c?
+ * xip_sparse_page() when found at pgoff.
*/
static void
__xip_unmap (struct address_space * mapping,
@@ -183,7 +213,11 @@ __xip_unmap (struct address_space * mapp
address = vma->vm_start +
((pgoff - vma->vm_pgoff) << PAGE_SHIFT);
BUG_ON(address < vma->vm_start || address >= vma->vm_end);
- page = ZERO_PAGE(0);
+ page = xip_sparse_page();
+ if (!page)
+ /* cannot allocate xip page, is not mapped anywhere */
+ goto out_unlock;
+
pte = page_check_address(page, mm, address, &ptl);
if (pte) {
/* Nuke the page table entry. */
@@ -196,6 +230,7 @@ __xip_unmap (struct address_space * mapp
page_cache_release(page);
}
}
+out_unlock:
spin_unlock(&mapping->i_mmap_lock);
}
@@ -245,12 +280,13 @@ xip_file_nopage(struct vm_area_struct *
/* unmap page at pgoff from all other vmas */
__xip_unmap(mapping, pgoff);
} else {
- /* not shared and writable, use ZERO_PAGE() */
- page = ZERO_PAGE(0);
+ /* not shared and writable, use xip_sparse_page() */
+ page = xip_sparse_page();
}
out:
- page_cache_get(page);
+ if (page)
+ page_cache_get(page);
return page;
}
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2007-02-26 18:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-16 12:22 Carsten Otte
2007-02-18 18:56 ` Hugh Dickins
2007-02-26 18:04 ` Carsten Otte [this message]
2007-03-01 18:59 ` [RFC] " Hugh Dickins
2007-03-27 15:37 ` Carsten Otte
2007-03-27 17:07 ` 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=1172513050.5685.21.camel@cotte.boeblingen.de.ibm.com \
--to=cotte@de.ibm.com \
--cc=hugh@veritas.com \
--cc=linux-mm@kvack.org \
--cc=nickpiggin@yahoo.com.au \
/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