lvm and locales memory issue

[Milan Broz <mbroz@redhat.com>]

On 02/18/2010 10:19 AM, Zdenek Kabelac wrote:
> As we discussed yesterday at the confcall the problem with mlockall() and way
> we cannot easily disable locales, because of posix complaince and
> internationalized error message.

So here is a solution. But what's the problem? :-)

For the kindly reader of lvm-devel not attending confcall(s), 
please can you describe what's the problem you are trying to solve?

Is it glibc locale handling bug? Or lvm uses locales the wrong way?
Which other programs are affected too?

Several programs use mlockall() (e.g. I am doing the same operation
as lvm in cryptsetup), some of them use locales, some not. 
Even some libraries can lock memory (gcrypt & safe pool allocation).

> How about adding some global{} configure option ?
> 
> e.i.:  "use_plain_C_locales = 0/1"

I couldn't resist but this seems to me like
We_have_no_idea_what_is_going_on_but_setting_this_to_zero_decreases_memory_use = 0 ;-)

Milan