On 04/08/2013 07:43 PM, Jamie Strandboge wrote:
> Recent kernels/glibc also now trigger reads for
> /proc/sys/vm/overcommit_memory. This is explained in both malloc(3) and
> proc(5). Basically, there are different memory allocation strategies and
> /proc/sys/vm/overcommit_memory contains the 'virtual memory accounting'
> mode. The update for the base abstraction gives read access to this file.
> 

Here is the glibc commit:
http://sourceware.org/git/?p=glibc.git;a=commit;h=9fab36eb583c0e585e83a01253299afed9ea9a11

Basically, glibc adjusts its malloc behavior based on the value of
/proc/sys/vm/overcommit_memory, which is why the read is needed.

-- 
Jamie Strandboge                 http://www.ubuntu.com/

Attachment: signature.asc
Description: OpenPGP digital signature

-- 
AppArmor mailing list
AppArmor@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/apparmor

Reply via email to