Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Meelis Roos <mroos@linux.ee>
To: linux-parisc@vger.kernel.org
Subject: mmap problem in localedef
Date: Mon, 5 Dec 2016 13:36:17 +0200 (EET)	[thread overview]
Message-ID: <alpine.LRH.2.20.1612051330040.25582@math.ut.ee> (raw)

I noticed that locale-gen fails to work on my gentoo. Before reporting 
to getnoo I tried to understand whether there is something specific to 
parisc and here is the relevant part of strace from localedef 
invocation:

1761  open("//usr/lib/locale/locale-archive.yvHI9a", O_RDWR|O_CREAT|O_EXCL, 0600) = 3
1761  write(3, "\336\2\1\t\0\0\0\0\0\0\0008\0\0\0\0\0\0\3\213\0\0*\274\0\0\0\0\0\0\35L"..., 56) = 56
1761  ftruncate64(3, 103860)            = 0
1761  mmap2(NULL, 536870912, PROT_NONE, MAP_SHARED, 3, 0) = 0xd79bd000
1761  mmap2(0xd7c00000, 103860, PROT_READ|PROT_WRITE, MAP_SHARED|MAP_FIXED, 3, 0) = -1 EINVAL (Invalid argument)
1761  unlink("//usr/lib/locale/locale-archive.yvHI9a") = 0
1761  write(2, "cannot map archive header", 25) = 25
1761  write(2, ": Invalid argument", 18) = 18
1761  write(2, "\n", 1)                 = 1
1761  exit_group(1)                     = ?

Do I read it correctly that it creates PROT_NONE mapping on file opened 
O_RDWR, then tries to create a PROT_READ|PROT_WRITE mapping from the 
same file at fixed location and fails?

Why should it fail - because the fixed location is not suitable?

-- 
Meelis Roos (mroos@linux.ee)

             reply	other threads:[~2016-12-05 11:36 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-05 11:36 Meelis Roos [this message]
2016-12-05 18:10 ` mmap problem in localedef Aaro Koskinen
2016-12-05 18:49   ` John David Anglin
2016-12-05 20:58     ` Aaro Koskinen
2016-12-05 21:17       ` John David Anglin
2016-12-05 23:50         ` John David Anglin
2017-04-01 18:37           ` Aaro Koskinen
2017-04-01 18:41             ` Rolf Eike Beer
2017-04-01 19:10               ` Aaro Koskinen
2017-04-02 14:08                 ` John David Anglin
2017-04-02 19:12                   ` Aaro Koskinen
2017-04-02 19:49                     ` John David Anglin
2017-04-02 20:13                       ` John David Anglin
2017-04-02 20:55                         ` John David Anglin
2017-04-02 21:45                       ` John David Anglin
2017-04-05 23:03                     ` John David Anglin
2017-04-11 12:01                       ` John David Anglin
2017-04-11 13:57                         ` Rolf Eike Beer
2017-04-16 19:22                           ` John David Anglin
2017-04-01 19:20             ` John David Anglin
2016-12-05 21:12     ` Meelis Roos
2016-12-05 21:17       ` Jeroen Roovers

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.LRH.2.20.1612051330040.25582@math.ut.ee \
    --to=mroos@linux.ee \
    --cc=linux-parisc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox