linux-kernel - [PATCH] doc: missing value 2 for randomize-va-space

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 2 Jul 2009 17:23:38 +0200
From:	Horst Schirmeier <horst@...irmeier.com>
To:	rdunlap@...otime.net
Cc:	linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
	trivial@...nel.org
Subject: [PATCH] doc: missing value 2 for randomize-va-space

The documentation for /proc/sys/kernel/* does not mention the possible
value 2 for randomize-va-space (but already mentions what it does).

Signed-off-by: Horst Schirmeier <horst@...irmeier.com>
---
 Documentation/sysctl/kernel.txt |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/sysctl/kernel.txt b/Documentation/sysctl/kernel.txt
index 322a00b..b2af4ef 100644
--- a/Documentation/sysctl/kernel.txt
+++ b/Documentation/sysctl/kernel.txt
@@ -310,7 +310,7 @@ that support this feature.
     loaded to random addresses. Also for PIE-linked binaries, the location
     of code start is randomized.
 
-    With heap randomization, the situation is a little bit more
+2 - With heap randomization, the situation is a little bit more
     complicated.
     There a few legacy applications out there (such as some ancient
     versions of libc.so.5 from 1996) that assume that brk area starts

-- 
PGP-Key 0xD40E0E7A
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/