Re: [PATCH mm] limit the mm->map_count not greater than sysctl_max_map_count

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxx.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>


[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]