linux-kernel - Re: [PATCH] Kbuild: set LC_MESSAGES=C (as LC

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 26 Dec 2009 12:04:57 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Roland Dreier <rdreier@...co.com>
CC:	Sergei Trofimovich <slyich@...il.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, Michal Marek <mmarek@...e.cz>,
	Sergei Trofimovich <slyfox@...ox.ru>
Subject: Re: [PATCH] Kbuild: set LC_MESSAGES=C (as LC_CTYPE=C is)

On 12/25/2009 05:17 PM, Roland Dreier wrote:
> 
>  > The whole reason with only setting some LC_* to C was to be able to
>  > leave LC_MESSAGES intact, but it seems it breaks on too many real-life
>  > systems.
> 
>  > As such, I suggest we should set LC_ALL=C and get rid of the rest of it:
> 
> Seems unfortunate to lose localized error messages.  (Although in my
> en_US.UTF-8 case, all I get is non-ASCII quote characters)
> 
> This all started because of the awk invocation in arch/x86/lib.  Maybe
> the best idea would be to confine the locale monkeying to that one
> place?
> 

It is also possible that setting only LC_COLLATE will solve the most
fundamental problem, which is the one of character ranges.  LC_COLLATE
probably will interfere less with LC_MESSAGES than the setting of LC_CTYPE.

It's still bloody broken that glibc malfunctions like that for an
LC_MESSAGES/LC_CTYPE intentional mismatch, but, sigh, that's glibc for you.

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/