This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug localedata/5033] locarchive does not provide fallback for mmap()
- From: "junkmailnotread at yahoo dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: Tue, 21 Feb 2012 14:42:33 +0000
- Subject: [Bug localedata/5033] locarchive does not provide fallback for mmap()
- Auto-submitted: auto-generated
- References: <bug-5033-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=5033
junkmailnotread at yahoo dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |junkmailnotread at yahoo
| |dot com
--- Comment #1 from junkmailnotread at yahoo dot com 2012-02-21 14:42:33 UTC ---
This is a serious bug and still present in glibc-2.13. Why no progress?
To clarify, localedef *fails* if /usr/lib/locale/locale-archive is located on a
file system - such as JFFS2 - which does not support the mmap(2) MAP_SHARED
flag.
As far as I can tell, any Linux kernel file system whose mmap handler is:
generic_file_readonly_mmap()
does not support MAP_SHARED. Currently, as of linux-3.3, these include:
9p
afs
jffs2
logfs
The bug is easy to demonstrate. Here, the root file system is a JFFS2 file
system, and /var/tmp is a tmpfs file system:
# ls -l /usr/lib/locale
total 0
# df /usr/lib/locale
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/root 78592 27816 50776 36% /
# localedef -f ISO-8859-1 -i en_GB en_GB.ISO-8859-1
cannot map archive header: Invalid argument
# rmdir /usr/lib/locale
# ln -s /var/tmp /usr/lib/locale
# df /usr/lib/locale
Filesystem 1K-blocks Used Available Use% Mounted on
none 30664 24 30640 1% /var
# localedef -f ISO-8859-1 -i en_GB en_GB.ISO-8859-1
# localedef --list
en_GB.iso88591
#
I've just spent a day tracking this bug down, only to discover it was reported
over 4 years ago.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.