Pavel Emelianov wrote: >>> Though I haven't >>>seen any problems with glibc for many years running OpenVZ and I think, >>>that if glibc will want to cache this getpid() value we can teach it to >>>uncache this value in case someone called unshare() with CLONE_NEWPIDS. >> >>glibc very much caches the results of getpid(). > > > Can you prove it? We have run OpenVZ for many years and with many > userspace configurations and we haven't seen the problems with > glibc ever. Pavel, but we always do full namespace entering with fork()'s and such actions. So we simply couldn't trigger getpid() caching. Thanks, Kirill _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/containers
