linux-kernel - Re: [PATCH] mm: disable `vm.max_map

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]

Message-ID: <20171127194603.GA28115@avx2>
Date:   Mon, 27 Nov 2017 22:46:03 +0300
From:   Alexey Dobriyan <adobriyan@...il.com>
To:     mikpelinux.gmail.com@...2
Cc:     linux-kernel@...r.kernel.org, mhocko@...nel.org,
        willy@...radead.org, ak@...ux.intel.com, linux-mm@...ck.org
Subject: Re: [PATCH] mm: disable `vm.max_map_count' sysctl limit

> vm.max_map_count

I always thought it is some kind of algorithmic complexity limiter and
kernel memory limiter. VMAs are under SLAB_ACCOUNT nowadays but ->mmap
list stays:

	$ chgrep -e 'for.*vma = vma->vm_next' | wc -l
	41

In particular readdir on /proc/*/map_files .

I'm saying you can not simply remove this sysctl.