[lvm-devel] lvm and locales memory issue

[Jakub Jelinek]

On Mon, Feb 22, 2010 at 06:51:00PM +0000, Alasdair G Kergon wrote:
> This workaround still does not address the fundamental problem:
> glibc is holding open a large mmaped file on behalf of the process and
> seemingly offering no way for the process to instruct it to close it without
> exiting.

Guess we disagree what is the fundamental problem.  IMHO it is a big app
calling mlockall after it has called lots of functions from lots of
libraries.  mlockall really is meant to be used only in very small, tightly
controlled apps,  requiring every library function to be mlockall aware and
have some API for flush before mlockall is unrealistical.

	Jakub