From: Arnd Bergmann <arnd@arndb.de>
To: michal.simek@petalogix.com
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
LTP <ltp-list@lists.sourceforge.net>,
John Williams <john.williams@petalogix.com>,
Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
Grant Likely <grant.likely@secretlab.ca>,
subrata@linux.vnet.ibm.com
Subject: Re: mmap syscall problem
Date: Fri, 3 Jul 2009 17:02:52 +0200 [thread overview]
Message-ID: <200907031702.52612.arnd@arndb.de> (raw)
In-Reply-To: <4A4DFB77.1080700@petalogix.com>
On Friday 03 July 2009, Michal Simek wrote:
> I am trying to solve problem with mmap syscall on Microblaze which I have.
> I am running mmap01 test program from LTP. In attachment is hacked
> version and inline version is below too.
Does this happen on microblaze-mmu or microblaze-nommu, or both?
The mmap code for the two is very different.
What file system is backing the temporary file?
For -nommu, there are a number of ristrictions from
Documentation/nommu-mmap.txt, in particular, MAP_FIXED is
forbidden, as is PROT_WRITE with regular files.
> Arnd: Anyway maybe worth to move sys_mmap2 to any generic location. What
> do you think?
Yes, that would be good. I actually have a patch for that somewhere in
my playground repository, but it build-breaks some architectures in the
current state. I'm planning to fix that (and do the same for execve
and maybe some of the other remaining arch specific syscalls) at some
point.
Arnd <><
next prev parent reply other threads:[~2009-07-03 15:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-03 12:37 mmap syscall problem Michal Simek
2009-07-03 15:02 ` Arnd Bergmann [this message]
2009-07-06 6:32 ` Michal Simek
2009-07-06 8:05 ` Arnd Bergmann
2009-07-06 12:07 ` Michal Simek
2009-07-06 12:14 ` Paul Mundt
2009-07-06 12:54 ` Michal Simek
2009-07-06 14:16 ` Arnd Bergmann
2009-07-06 14:43 ` Michal Simek
2009-07-06 15:05 ` Arnd Bergmann
2009-07-06 15:19 ` Michal Simek
2009-07-07 0:44 ` Valdis.Kletnieks
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=200907031702.52612.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=akpm@linux-foundation.org \
--cc=grant.likely@secretlab.ca \
--cc=john.williams@petalogix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ltp-list@lists.sourceforge.net \
--cc=michal.simek@petalogix.com \
--cc=mingo@elte.hu \
--cc=subrata@linux.vnet.ibm.com \
/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