linux-kernel - Re: [PATCH v2] 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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <CA+55aFy-5TUA38AE-6EiAPD0uB2g7=pNmqhjHTiT8fX_+z-q0g@mail.gmail.com>
Date:	Sun, 24 Apr 2016 16:03:04 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Konstantin Khlebnikov <koct9i@...il.com>
Cc:	linux-mm <linux-mm@...ck.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Cyrill Gorcunov <gorcunov@...nvz.org>,
	Christian Borntraeger <borntraeger@...ibm.com>
Subject: Re: [PATCH v2] mm: enable RLIMIT_DATA by default with workaround for valgrind

On Sun, Apr 24, 2016 at 1:29 PM, Konstantin Khlebnikov <koct9i@...il.com> wrote:
>
> This patch checks current usage also against rlim_max if rlim_cur is zero.
> This is safe because task anyway can increase rlim_cur up to rlim_max.
> Size of brk is still checked against rlim_cur, so this part is completely
> compatible - zero rlim_cur forbids brk() but allows private mmap().

Ack. And I'll assume this comes through -mm like the original patches did.

          Linus