public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Oskari Pirhonen <xxc3ncoredxx@gmail.com>
To: Alex Colomar <alx.manpages@gmail.com>
Cc: lnx-man <linux-man@vger.kernel.org>
Subject: Re: Doubts about mmap(2)
Date: Thu, 18 May 2023 23:47:41 -0500	[thread overview]
Message-ID: <ZGb_bYkms3z4urdc@dj3ntoo> (raw)
In-Reply-To: <13993515-e3af-3c40-1351-24aaf8814bf6@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2049 bytes --]

On Thu, May 18, 2023 at 11:03:14 +0200, Alex Colomar wrote:
> On 5/18/23 10:53, Alex Colomar wrote:
> > Hi!
> > 
> > I believe mmap(2) is confusing (see the emboldened parts):
> > 
> > DESCRIPTION
> >         mmap()  creates  a  new mapping in the virtual address space of
> >         the calling process.  **The starting address for the new  mapping
> >         is specified in addr.**  The length argument specifies the length
> >         of the mapping (which must be greater than 0).
> > 
> >         If addr is NULL, then the kernel chooses the (page‐aligned) ad‐
> >         dress at which to create the mapping; this is the most portable
> >         method  of  creating  a new mapping.  **If addr is not NULL, then
> >         the kernel takes it as a hint about where to place the mapping;
> >         on Linux, the kernel will pick a nearby page boundary** (but  al‐
> >         ways    above    or   equal   to   the   value   specified   by
> >         /proc/sys/vm/mmap_min_addr) and attempt to create  the  mapping
> >         there.   If  another  mapping  already exists there, the kernel
> >         picks a new address that may or may not  depend  on  the  hint.
> >         The address of the new mapping is returned as the result of the
> >         call.
> > 
> > 
> > The first emboldened sentence contradicts the second.  It's not the
> > starting address, but just a hint to find a nearby (>=) starting
> 
> I was a bit wrong there.  It's >= mmap_min_addr, not >= hint.  But the
> suggestion below holds.
> 
> > address.  How about saying this?:
> > 
> >      A hint for the starting address for the new mapping is specified in
> >      addr.
> > 

I think describing the default behavior first is a good idea. If a user
needs an exact address they can read further for MAP_FIXED/_NOREPLACE
(and the potential footguns involved).

- Oskari

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

      reply	other threads:[~2023-05-19  4:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-18  8:53 Doubts about mmap(2) Alex Colomar
2023-05-18  9:03 ` Alex Colomar
2023-05-19  4:47   ` Oskari Pirhonen [this message]

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=ZGb_bYkms3z4urdc@dj3ntoo \
    --to=xxc3ncoredxx@gmail.com \
    --cc=alx.manpages@gmail.com \
    --cc=linux-man@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