From: "Bao C. Ha" <baoha@sensoria.com>
To: <linux-kernel@vger.kernel.org>
Subject: Different old_mmap behavior between 2.4.5 and 2.4.8
Date: Mon, 10 Sep 2001 18:30:55 -0700 [thread overview]
Message-ID: <028701c13a61$67bf17e0$456c020a@SENSORIA> (raw)
We are moving from kernel 2.4.5 to kernel 2.4.8 and above.
One of our applications broke due to different behaviors
of the system call old_mmap.
In kernel 2.4.5:
307 old_mmap(0x7b7f7000, 36864, PROT_READ|PROT_WRITE|PROT_EXEC,
MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7b7f7000
In kernel 2.4.8:
[pid 313] old_mmap(0x7b7f7000, 36864, PROT_READ|PROT_WRITE|PROT_EXEC,
MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7b7f8000
In 2.4.5, we request 0x7b7f7000 and get the same area back.
In 2.4.8, we also request 0x7b7f7000, but we are getting a
different area pointed by 0x7b7f8000.
Is this supposed to be the correct behavior? What changes
make the newer kernels to return different pointers? We
are running on the sh4 architecture but I think these calls
come from malloc() which should be arch-independent.
Appreciate any pointers/suggestions.
Thanks.
Bao
next reply other threads:[~2001-09-11 1:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-11 1:30 Bao C. Ha [this message]
2001-09-11 1:49 ` Different old_mmap behavior between 2.4.5 and 2.4.8 Benjamin LaHaise
2001-09-11 18:31 ` Bao C. Ha
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='028701c13a61$67bf17e0$456c020a@SENSORIA' \
--to=baoha@sensoria.com \
--cc=linux-kernel@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