Bug#414955: marked as done (mremap doesn't match kernel or man page)
Your message dated Thu, 12 Apr 2007 11:55:01 +0200
with message-id <461E01F5.3040800@aurel32.net>
and subject line Bug#414955: mremap doesn't match kernel or man page
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: libc6.1-dev
Version: 2.3.6.ds1-13
Since 2.3.31, the Linux kernel has allowed an additional 'flags' value for
mremap(): MREMAP_FIXED (defined with the value 2), which serves a similar
purpose to the mmap() MAP_FIXED flag. If this flag is supplied, then mremap()
employs a fifth argument, 'new_address', which specifies a fixed address to
which the mapping should be relocated.
Currently, glibc does not expose the MREMAP_FIXED definition and the
mremap() prototype does not expose the fifth argument. Can these
definitions please be exposed in glibc? I believe it's fixed in
upstream version 2.4.?
Peter C
--- End Message ---
--- Begin Message ---
- To: Peter Chubb <peterc@gelato.unsw.edu.au>, 414955-done@bugs.debian.org
- Subject: Re: Bug#414955: mremap doesn't match kernel or man page
- From: Aurelien Jarno <aurelien@aurel32.net>
- Date: Thu, 12 Apr 2007 11:55:01 +0200
- Message-id: <461E01F5.3040800@aurel32.net>
- In-reply-to: <17912.37032.418417.188445@berry.ken.nicta.com.au>
- References: <17912.37032.418417.188445@berry.ken.nicta.com.au>
Version: 2.5-1
Peter Chubb a écrit :
> Package: libc6.1-dev
> Version: 2.3.6.ds1-13
>
> Since 2.3.31, the Linux kernel has allowed an additional 'flags' value for
> mremap(): MREMAP_FIXED (defined with the value 2), which serves a similar
> purpose to the mmap() MAP_FIXED flag. If this flag is supplied, then mremap()
> employs a fifth argument, 'new_address', which specifies a fixed address to
> which the mapping should be relocated.
>
> Currently, glibc does not expose the MREMAP_FIXED definition and the
> mremap() prototype does not expose the fifth argument. Can these
> definitions please be exposed in glibc? I believe it's fixed in
> upstream version 2.4.?
>
Yep it is fixed in version 2.4 and later. The current version of the
glibc in unstable is 2.5-1, so I am closing this bug.
--
.''`. Aurelien Jarno | GPG: 1024D/F1BCDB73
: :' : Debian developer | Electrical Engineer
`. `' aurel32@debian.org | aurelien@aurel32.net
`- people.debian.org/~aurel32 | www.aurel32.net
--- End Message ---
Reply to: