[master] 0945a8f41 Mention another source of stack increase

Dridi Boukelmoune dridi.boukelmoune at gmail.com
Mon Mar 11 18:37:07 UTC 2019

commit 0945a8f41bb567b01432f6a82e61f01a96ac39ba
Author: Dridi Boukelmoune <dridi.boukelmoune at gmail.com>
Date:   Mon Mar 11 19:35:02 2019 +0100

    Mention another source of stack increase

diff --git a/doc/sphinx/whats-new/changes-trunk.rst b/doc/sphinx/whats-new/changes-trunk.rst
index 2501c937d..56cf52bf3 100644
--- a/doc/sphinx/whats-new/changes-trunk.rst
+++ b/doc/sphinx/whats-new/changes-trunk.rst
@@ -46,7 +46,11 @@ external libraries that are not under control of the Varnish project
 (such as glibc). This may also have been related to stack overflow
 issues on some platforms when recent versions of `jemalloc`_, the
 recommended memory allocator for Varnish, have been used together with
-`pcre`_ with JIT compilation enabled.
+`pcre`_ with JIT compilation enabled. Compiler hardening flags may
+also increase stack usage and on some systems such stack protector
+flags may be enabled by default. With the addition of new mitigations
+to new compiler releases, stack consumption may also increase on that
 Tests have shown that Varnish runs stably with the new default stack
 size on a number of platforms, under conditions that previously may

More information about the varnish-commit mailing list