linux-kernel - Re: [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-prev] [day] [month] [year] [list]

Date:	Fri, 3 Jul 2009 12:26:31 +0200 (CEST)
From:	Jiri Kosina <jkosina@...e.cz>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Horst Schirmeier <horst@...irmeier.com>, rdunlap@...otime.net,
	linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] doc: missing value 2 for randomize-va-space

On Fri, 3 Jul 2009, Ingo Molnar wrote:

> > > > >      There a few legacy applications out there (such as some ancient
> > > > 
> > > > ... would you please fix this typo/grammo as well? (There a few ...)
> > > > 
> > > > >      versions of libc.so.5 from 1996) that assume that brk area starts
> > > > 
> > > > Also, the text itself doesn't seem to be super-clear ... namely, it 
> > > > describes what CONFIG_COMPAT_BRK is about, but doesn't really clarify how 
> > > > exactly does this correlate with randomize_va_space == 2. Would you mind 
> > > > also fixing this bit?
> > > 
> > > I hope I didn't misread the sources :-)  Opinions?
> > > 
> > > ---
> > > 
> > > The documentation for /proc/sys/kernel/* does not mention the possible
> > > value 2 for randomize-va-space yet.  While being there, doing some
> > > reformatting, fixing grammar problems and clarifying the correlations
> > > between randomize-va-space, kernel parameter "norandmaps" and the
> > > CONFIG_COMPAT_BRK option.
> > >                                                     
> > > Signed-off-by: Horst Schirmeier <horst@...irmeier.com>
> > 
> > Acked-by: Jiri Kosina <jkosina@...e.cz>
> > 
> > Ingo, will you take this through your tree?
> > 
> > > 
> > > ---
> > >  Documentation/sysctl/kernel.txt |   30 +++++++++++++++++-------------
> > >  1 files changed, 17 insertions(+), 13 deletions(-)
> 
> This could go to your or Randy's docs tree, right? (would be fine by 
> me)

Sure, I basically just wanted your ACK, as you were the last one touching 
the respective code.

I will queue it, thanks.

-- 
Jiri Kosina
SUSE Labs
--
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/