linux-kernel - Re: [PATCH mm] limit the mm->map_count not greater than sysctl_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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4F8EC161.5050307@gmail.com>
Date:	Wed, 18 Apr 2012 21:28:01 +0800
From:	Cong Wang <xiyou.wangcong@...il.com>
To:	Li Zhong <zhong@...ux.vnet.ibm.com>
CC:	linux-kernel@...r.kernel.org, linux-mm@...ck.org,
	akpm@...ux-foundation.org
Subject: Re: [PATCH mm] limit the mm->map_count not greater than sysctl_max_map_count

On 04/18/2012 05:27 PM, Li Zhong wrote:
> When reading the mmap codes, I found the checking of mm->map_count
> against sysctl_max_map_count is not consistent. At some places, ">" is
> used; at some other places, ">=" is used.
>
> This patch changes ">" to">=", so they are consistent, and makes sure
> the value is not greater (one more) than sysctl_max_map_count.
>

Well, according to Documentation/sysctl/vm.txt,

max_map_count:

This file contains the maximum number of memory map areas a process
may have. [...]

I think ->map_count == sysctl_max_map_count should be allowed, so using 
'>' is correct.
--
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/