From: Rust Maintainers <pkg-rust-maintainers@lists.alioth.debian.org>
Date: Wed, 9 Aug 2017 02:49:55 +0000 (+0100)
Subject: u-skip-main-thread-stack-guard
X-Git-Tag: archive/raspbian/1.19.0+dfsg3-4+rpi1^2~24
X-Git-Url: https://dgit.raspbian.org/?a=commitdiff_plain;h=99af1cced1511f92e9956eba75e7d691e1ecc206;p=rustc.git

u-skip-main-thread-stack-guard

commit be509b3387aebb453b09a4942cf902c7d05a0f1e
Author: Josh Stone <jistone@redhat.com>
Date:   Wed Jul 5 12:03:17 2017 -0700

    Skip the main thread's manual stack guard on Linux

    Linux doesn't allocate the whole stack right away, and the kernel has
    its own stack-guard mechanism to fault when growing too close to an
    existing mapping.  If we map our own guard, then the kernel starts
    enforcing a rather large gap above that, rendering much of the possible
    stack space useless.

    Instead, we'll just note where we expect rlimit to start faulting, so
    our handler can report "stack overflow", and trust that the kernel's own
    stack guard will work.

    Fixes #43052.


Gbp-Pq: Name u-skip-main-thread-stack-guard.patch
---

diff --git a/src/libstd/sys/unix/thread.rs b/src/libstd/sys/unix/thread.rs
index 1642baa34d..1574774661 100644
--- a/src/libstd/sys/unix/thread.rs
+++ b/src/libstd/sys/unix/thread.rs
@@ -264,23 +264,37 @@ pub mod guard {
                 as *mut libc::c_void;
         }
 
-        // Rellocate the last page of the stack.
-        // This ensures SIGBUS will be raised on
-        // stack overflow.
-        let result = mmap(stackaddr, psize, PROT_NONE,
-                          MAP_PRIVATE | MAP_ANON | MAP_FIXED, -1, 0);
-
-        if result != stackaddr || result == MAP_FAILED {
-            panic!("failed to allocate a guard page");
-        }
-
-        let offset = if cfg!(any(target_os = "linux", target_os = "freebsd")) {
-            2
+        if cfg!(target_os = "linux") {
+            // Linux doesn't allocate the whole stack right away, and
+            // the kernel has its own stack-guard mechanism to fault
+            // when growing too close to an existing mapping.  If we map
+            // our own guard, then the kernel starts enforcing a rather
+            // large gap above that, rendering much of the possible
+            // stack space useless.  See #43052.
+            //
+            // Instead, we'll just note where we expect rlimit to start
+            // faulting, so our handler can report "stack overflow", and
+            // trust that the kernel's own stack guard will work.
+            Some(stackaddr as usize)
         } else {
-            1
-        };
+            // Reallocate the last page of the stack.
+            // This ensures SIGBUS will be raised on
+            // stack overflow.
+            let result = mmap(stackaddr, psize, PROT_NONE,
+                              MAP_PRIVATE | MAP_ANON | MAP_FIXED, -1, 0);
+
+            if result != stackaddr || result == MAP_FAILED {
+                panic!("failed to allocate a guard page");
+            }
 
-        Some(stackaddr as usize + offset * psize)
+            let offset = if cfg!(target_os = "freebsd") {
+                2
+            } else {
+                1
+            };
+
+            Some(stackaddr as usize + offset * psize)
+        }
     }
 
     #[cfg(target_os = "solaris")]