Re: [discuss] [PATCH] Inconsistent mmap()/mremap() flags

> 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.

-Andi

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Follow-Ups:
- Re: [discuss] [PATCH] Inconsistent mmap()/mremap() flags
  - From: Hugh Dickins <[email protected]>

References:
- Re: [PATCH] Inconsistent mmap()/mremap() flags
  - From: Thayne Harbaugh <[email protected]>
- Re: [PATCH] Inconsistent mmap()/mremap() flags
  - From: Hugh Dickins <[email protected]>

Prev by Date: Re: [PATCH] blacklist NCQ on Seagate Barracuda ST380817AS
Next by Date: [TOMOYO 00/15](repost) TOMOYO Linux - MAC based on process invocation history.
Previous by thread: Re: [PATCH] Inconsistent mmap()/mremap() flags
Next by thread: Re: [discuss] [PATCH] Inconsistent mmap()/mremap() flags
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]