linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Thayne Harbaugh <thayne@c2.net>
To: Hugh Dickins <hugh@veritas.com>
Cc: Andi Kleen <ak@suse.de>,
	discuss@x86-64.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: Re: [discuss] [PATCH] Inconsistent mmap()/mremap() flags
Date: Tue, 02 Oct 2007 09:21:26 -0600	[thread overview]
Message-ID: <1191338486.5200.71.camel@phantasm.home.enterpriseandprosperity.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0710021505400.2156@blonde.wat.veritas.com>

On Tue, 2007-10-02 at 15:16 +0100, Hugh Dickins wrote:
> On Tue, 2 Oct 2007, Andi Kleen wrote:
> > 
> > > First call mmap with a low hint address, the new size you'll be wanting
> > > from the mremap, PROT_NONE, MAP_ANONYMOUS, -1, 0.  Then call mremap with
> > > old address, old size, new size, MREMAP_MAYMOVE|MREMAP_FIXED, and new
> > > address as returned by the preparatory mmap.
> > 
> > That's racy unfortunately in a multithreaded process. They would need to loop.
> 
> Perhaps.  Though I don't see what your loop would be doing;
> and the mapping established by the first thread would only
> be vulnerable to another thread if that were really set on
> interfering (an un-FIXED mmap by another thread will keep
> away from the area assigned to the first).
> 
> Certainly a two-stage procedure has to be weaker than one stage,
> but it is just how MAP_FIXED is normally used (isn't it?): first
> stake out an arena for all that's needed without MAP_FIXED, then
> fit into it the actual mappings required using MAP_FIXED.  Blind
> use of MAP_FIXED is always in danger of unmapping something vital.
> 
> But whether the two-stage procedure is good enough for Thayne's
> purpose, he'll have to judge for himself.

I think my eyes have been opened enough so that I can get things to work
- it's certainly better in many respects than using MAP_32BIT with its
many limitations.

Thank you.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

      reply	other threads:[~2007-10-02 15:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-28  5:46 [PATCH] Inconsistent mmap()/mremap() flags Thayne Harbaugh
2007-10-01 11:13 ` Andi Kleen
2007-10-02  2:57   ` Thayne Harbaugh
2007-10-02  5:15     ` Andi Kleen
2007-10-02  7:06       ` Thayne Harbaugh
2007-10-02 12:19         ` Hugh Dickins
2007-10-02 13:45           ` [discuss] " Andi Kleen
2007-10-02 14:16             ` Hugh Dickins
2007-10-02 15:21               ` Thayne Harbaugh [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=1191338486.5200.71.camel@phantasm.home.enterpriseandprosperity.com \
    --to=thayne@c2.net \
    --cc=ak@suse.de \
    --cc=discuss@x86-64.org \
    --cc=hugh@veritas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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;
as well as URLs for NNTP newsgroup(s).