mmap.2: Some rewording of the description of MAP_STACK

Reword a little to allow for the fact that there are now
*two* reasons to consider using this flag.

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2019-11-14 13:00:01 +01:00
parent d3d881232b
commit 91243dad42
1 changed files with 7 additions and 4 deletions

View File

@ -404,10 +404,13 @@ is supported for private mappings only since Linux 2.6.23.
Allocate the mapping at an address suitable for a process
or thread stack.
.IP
This flag is currently a no-op,
but is used in the glibc threading implementation so that
if some architectures require special treatment for stack allocations,
support can later be transparently implemented for glibc.
This flag is currently a no-op on Linux.
However, by employing this flag, applications can ensure that
they transparently obtain support if the flag
is implemented in the future.
Thus, it is used in the glibc threading implementation to allow for
the fact that some architectures may (later) require special treatment
for stack allocations.
.\" See http://lwn.net/Articles/294642 "Tangled up in threads", 19 Aug 08
.\" commit cd98a04a59e2f94fa64d5bf1e26498d27427d5e7
.\" http://thread.gmane.org/gmane.linux.kernel/720412