You know what sucks? Determining the owner of anonymous private or shared mappings? I feel like CONFIG_ANON_VMA_NAME could be really useful, but it's behind both a kernel config and a glibc tunable GLIBC_TUNABLES=glibc.mem.decorate_maps=1 ... we could make this better?
@codonell male the tunable a default maybe?
@zatrazz We can't yet because of the VMA merging consequences?
@codonell It is my understanding that setting a PR_SET_VMA_ANON_NAME to anonymous area might prevent that area from being merged with adjacent virtual memory areas. I am not sure if this would really matter for glibc current uses.