delete a .27 patch

diff --git a/review-2.6.27/mm-keep-a-guard-page-below-a-grow-down-stack-segment.patch b/review-2.6.27/mm-keep-a-guard-page-below-a-grow-down-stack-segment.patch
deleted file mode 100644 (file)
index c3fd2aa..0000000
--- a/review-2.6.27/mm-keep-a-guard-page-below-a-grow-down-stack-segment.patch
+++ /dev/null
@@ -1,72 +0,0 @@
-From 320b2b8de12698082609ebbc1a17165727f4c893 Mon Sep 17 00:00:00 2001
-From: Linus Torvalds <torvalds@linux-foundation.org>
-Date: Thu, 12 Aug 2010 17:54:33 -0700
-Subject: mm: keep a guard page below a grow-down stack segment
-
-From: Linus Torvalds <torvalds@linux-foundation.org>
-
-commit 320b2b8de12698082609ebbc1a17165727f4c893 upstream.
-
-This is a rather minimally invasive patch to solve the problem of the
-user stack growing into a memory mapped area below it.  Whenever we fill
-the first page of the stack segment, expand the segment down by one
-page.
-
-Now, admittedly some odd application might _want_ the stack to grow down
-into the preceding memory mapping, and so we may at some point need to
-make this a process tunable (some people might also want to have more
-than a single page of guarding), but let's try the minimal approach
-first.
-
-Tested with trivial application that maps a single page just below the
-stack, and then starts recursing.  Without this, we will get a SIGSEGV
-_after_ the stack has smashed the mapping.  With this patch, we'll get a
-nice SIGBUS just as the stack touches the page just above the mapping.
-
-Requested-by: Keith Packard <keithp@keithp.com>
-Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
-Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
-
----
- mm/memory.c |   23 +++++++++++++++++++++++
- 1 file changed, 23 insertions(+)
-
---- a/mm/memory.c
-+++ b/mm/memory.c
-@@ -2396,6 +2396,26 @@ out_nomap:
- }
- 
- /*
-+ * This is like a special single-page "expand_downwards()",
-+ * except we must first make sure that 'address-PAGE_SIZE'
-+ * doesn't hit another vma.
-+ *
-+ * The "find_vma()" will do the right thing even if we wrap
-+ */
-+static inline int check_stack_guard_page(struct vm_area_struct *vma, unsigned long address)
-+{
-+      address &= PAGE_MASK;
-+      if ((vma->vm_flags & VM_GROWSDOWN) && address == vma->vm_start) {
-+              address -= PAGE_SIZE;
-+              if (find_vma(vma->vm_mm, address) != vma)
-+                      return -ENOMEM;
-+
-+              expand_stack(vma, address);
-+      }
-+      return 0;
-+}
-+
-+/*
-  * We enter with non-exclusive mmap_sem (to exclude vma changes,
-  * but allow concurrent faults), and pte mapped but not yet locked.
-  * We return with mmap_sem still held, but pte unmapped and unlocked.
-@@ -2408,6 +2428,9 @@ static int do_anonymous_page(struct mm_s
-       spinlock_t *ptl;
-       pte_t entry;
- 
-+      if (check_stack_guard_page(vma, address) < 0)
-+              return VM_FAULT_SIGBUS;
-+
-       /* Allocate our own private page. */
-       pte_unmap(page_table);
- 

diff --git a/review-2.6.27/series b/review-2.6.27/series
index 15b2f61b76e97605bf59bb6c08f7fbcf72d70884..b343909af22e62e356e77fd97f858d0a7528719e 100644 (file)
--- a/review-2.6.27/series
+++ b/review-2.6.27/series
@@ -9,6 +9,3 @@ jfs-don-t-allow-os2-xattr-namespace-overlap-with-others.patch
 xen-drop-xen_sched_clock-in-favour-of-using-plain-wallclock-time.patch
 bdi-register-sysfs-bdi-device-only-once-per-queue.patch
 mm-backing-dev.c-remove-recently-added-warn_on.patch
-mm-keep-a-guard-page-below-a-grow-down-stack-segment.patch
-mm-fix-missing-page-table-unmap-for-stack-guard-page-failure-case.patch
-x86-don-t-send-sigbus-for-kernel-page-faults.patch