linux-kernel - Re: [PATCH] mm: enable RLIMIT_DATA by default with workaround for valgrind

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 for Android: free password hash cracker in your pocket

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

Date:	Sun, 24 Apr 2016 16:22:57 +0300
From:	Cyrill Gorcunov <gorcunov@...il.com>
To:	Konstantin Khlebnikov <koct9i@...il.com>
Cc:	linux-mm@...ck.org, Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org,
	Christian Borntraeger <borntraeger@...ibm.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH] mm: enable RLIMIT_DATA by default with workaround for
 valgrind

On Sun, Apr 24, 2016 at 11:07:23AM +0300, Konstantin Khlebnikov wrote:
> Since commit 84638335900f ("mm: rework virtual memory accounting")
> RLIMIT_DATA limits both brk() and private mmap() but this's disabled by
> default because of incompatibility with older versions of valgrind.
...
Reviewed-by: Cyrill Gorcunov <gorcunov@...nvz.org>

Thank you!