From: Michal Hocko <mhocko@kernel.org> To: Michael Kerrisk <mtk.manpages@gmail.com> Cc: linux-api@vger.kernel.org, Khalid Aziz <khalid.aziz@oracle.com>, Michael Ellerman <mpe@ellerman.id.au>, Andrew Morton <akpm@linux-foundation.org>, Russell King - ARM Linux <linux@armlinux.org.uk>, Andrea Arcangeli <aarcange@redhat.com>, linux-mm@kvack.org, LKML <linux-kernel@vger.kernel.org>, linux-arch@vger.kernel.org, Florian Weimer <fweimer@redhat.com>, John Hubbard <jhubbard@nvidia.com>, Matthew Wilcox <willy@infradead.org>, Michal Hocko <mhocko@suse.com> Subject: [PATCH 1/2] mmap.2: document new MAP_FIXED_SAFE flag Date: Wed, 13 Dec 2017 10:31:09 +0100 [thread overview] Message-ID: <20171213093110.3550-1-mhocko@kernel.org> (raw) In-Reply-To: <20171213092550.2774-1-mhocko@kernel.org> From: Michal Hocko <mhocko@suse.com> 4.16+ kernels offer a new MAP_FIXED_SAFE flag which allows the caller to atomicaly probe for a given address range. [wording heavily updated by John Hubbard <jhubbard@nvidia.com>] Signed-off-by: Michal Hocko <mhocko@suse.com> --- man2/mmap.2 | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) diff --git a/man2/mmap.2 b/man2/mmap.2 index a5a8eb47a263..02d391697ce6 100644 --- a/man2/mmap.2 +++ b/man2/mmap.2 @@ -227,6 +227,22 @@ in mind that the exact layout of a process' memory map is allowed to change significantly between kernel versions, C library versions, and operating system releases. .TP +.BR MAP_FIXED_SAFE " (since Linux 4.16)" +Similar to MAP_FIXED with respect to the +.I +addr +enforcement, but different in that MAP_FIXED_SAFE never clobbers a pre-existing +mapped range. If the requested range would collide with an existing +mapping, then this call fails with +.B EEXIST. +This flag can therefore be used as a way to atomically (with respect to other +threads) attempt to map an address range: one thread will succeed; all others +will report failure. Please note that older kernels which do not recognize this +flag will typically (upon detecting a collision with a pre-existing mapping) +fall back to a "non-MAP_FIXED" type of behavior: they will return an address that +is different than the requested one. Therefore, backward-compatible software +should check the returned address against the requested address. +.TP .B MAP_GROWSDOWN This flag is used for stacks. It indicates to the kernel virtual memory system that the mapping @@ -451,6 +467,12 @@ is not a valid file descriptor (and .B MAP_ANONYMOUS was not set). .TP +.B EEXIST +range covered by +.IR addr , +.IR length +is clashing with an existing mapping. +.TP .B EINVAL We don't like .IR addr , -- 2.15.0 -- 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>
WARNING: multiple messages have this Message-ID (diff)
From: Michal Hocko <mhocko@kernel.org> To: Michael Kerrisk <mtk.manpages@gmail.com> Cc: linux-api@vger.kernel.org, Khalid Aziz <khalid.aziz@oracle.com>, Michael Ellerman <mpe@ellerman.id.au>, Andrew Morton <akpm@linux-foundation.org>, Russell King - ARM Linux <linux@armlinux.org.uk>, Andrea Arcangeli <aarcange@redhat.com>, linux-mm@kvack.org, LKML <linux-kernel@vger.kernel.org>, linux-arch@vger.kernel.org, Florian Weimer <fweimer@redhat.com>, John Hubbard <jhubbard@nvidia.com>, Matthew Wilcox <willy@infradead.org>, Michal Hocko <mhocko@suse.com> Subject: [PATCH 1/2] mmap.2: document new MAP_FIXED_SAFE flag Date: Wed, 13 Dec 2017 10:31:09 +0100 [thread overview] Message-ID: <20171213093110.3550-1-mhocko@kernel.org> (raw) Message-ID: <20171213093109.ebQW8s1S3ZhNLP8oP_LuNsN6IU-qwjOfvvBJbor9tvc@z> (raw) In-Reply-To: <20171213092550.2774-1-mhocko@kernel.org> From: Michal Hocko <mhocko@suse.com> 4.16+ kernels offer a new MAP_FIXED_SAFE flag which allows the caller to atomicaly probe for a given address range. [wording heavily updated by John Hubbard <jhubbard@nvidia.com>] Signed-off-by: Michal Hocko <mhocko@suse.com> --- man2/mmap.2 | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) diff --git a/man2/mmap.2 b/man2/mmap.2 index a5a8eb47a263..02d391697ce6 100644 --- a/man2/mmap.2 +++ b/man2/mmap.2 @@ -227,6 +227,22 @@ in mind that the exact layout of a process' memory map is allowed to change significantly between kernel versions, C library versions, and operating system releases. .TP +.BR MAP_FIXED_SAFE " (since Linux 4.16)" +Similar to MAP_FIXED with respect to the +.I +addr +enforcement, but different in that MAP_FIXED_SAFE never clobbers a pre-existing +mapped range. If the requested range would collide with an existing +mapping, then this call fails with +.B EEXIST. +This flag can therefore be used as a way to atomically (with respect to other +threads) attempt to map an address range: one thread will succeed; all others +will report failure. Please note that older kernels which do not recognize this +flag will typically (upon detecting a collision with a pre-existing mapping) +fall back to a "non-MAP_FIXED" type of behavior: they will return an address that +is different than the requested one. Therefore, backward-compatible software +should check the returned address against the requested address. +.TP .B MAP_GROWSDOWN This flag is used for stacks. It indicates to the kernel virtual memory system that the mapping @@ -451,6 +467,12 @@ is not a valid file descriptor (and .B MAP_ANONYMOUS was not set). .TP +.B EEXIST +range covered by +.IR addr , +.IR length +is clashing with an existing mapping. +.TP .B EINVAL We don't like .IR addr , -- 2.15.0
next prev parent reply other threads:[~2017-12-13 9:31 UTC|newest] Thread overview: 82+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-12-13 9:25 [PATCH v2 0/2] mm: introduce MAP_FIXED_SAFE Michal Hocko 2017-12-13 9:25 ` Michal Hocko 2017-12-13 9:25 ` [PATCH 1/2] " Michal Hocko 2017-12-13 9:25 ` Michal Hocko [not found] ` <20171213092550.2774-2-mhocko-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> 2017-12-13 12:50 ` Matthew Wilcox 2017-12-13 12:50 ` Matthew Wilcox 2017-12-13 13:01 ` Michal Hocko 2017-12-13 13:01 ` Michal Hocko 2017-12-13 9:25 ` [PATCH 2/2] fs, elf: drop MAP_FIXED usage from elf_map Michal Hocko 2017-12-13 9:25 ` Michal Hocko 2017-12-16 0:49 ` [2/2] " Andrei Vagin 2017-12-18 9:13 ` Michal Hocko 2017-12-18 9:13 ` Michal Hocko 2017-12-18 18:12 ` Andrei Vagin 2017-12-18 18:12 ` Andrei Vagin 2017-12-13 9:31 ` Michal Hocko [this message] 2017-12-13 9:31 ` [PATCH 1/2] mmap.2: document new MAP_FIXED_SAFE flag Michal Hocko 2017-12-13 9:31 ` [PATCH 2/2] mmap.2: MAP_FIXED updated documentation Michal Hocko 2017-12-13 9:31 ` Michal Hocko 2017-12-13 12:55 ` Pavel Machek 2017-12-13 12:55 ` Pavel Machek 2017-12-13 13:03 ` Cyril Hrubis 2017-12-13 13:03 ` Cyril Hrubis 2017-12-13 13:04 ` Michal Hocko 2017-12-13 13:09 ` Pavel Machek 2017-12-13 13:09 ` Pavel Machek 2017-12-13 13:16 ` Michal Hocko 2017-12-13 13:16 ` Michal Hocko [not found] ` <20171213131640.GJ25185-2MMpYkNvuYDjFM9bn6wA6Q@public.gmane.org> 2017-12-13 13:21 ` Pavel Machek 2017-12-13 13:21 ` Pavel Machek 2017-12-13 13:35 ` Michal Hocko 2017-12-13 13:35 ` Michal Hocko 2017-12-13 14:40 ` Cyril Hrubis 2017-12-13 14:40 ` Cyril Hrubis 2017-12-13 23:19 ` Kees Cook 2017-12-13 23:19 ` Kees Cook [not found] ` <CAGXu5jLqE6cUxk-Girx6PG7upEzz8jmu1OH_3LVC26iJc2vTxQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 2017-12-14 7:07 ` Michal Hocko 2017-12-14 7:07 ` Michal Hocko 2017-12-18 19:12 ` Michael Kerrisk (man-pages) 2017-12-18 19:12 ` Michael Kerrisk (man-pages) 2017-12-18 20:19 ` Kees Cook 2017-12-18 20:19 ` Kees Cook 2017-12-18 20:33 ` Matthew Wilcox 2017-12-18 20:33 ` Matthew Wilcox [not found] ` <CAGXu5jJ289R9koVoHmxcvUWr6XHSZR2p0qq3WtpNyN-iNSvrNQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 2017-12-21 12:38 ` Michael Ellerman 2017-12-21 12:38 ` Michael Ellerman 2017-12-21 14:59 ` known bad patch in -mm tree was " Pavel Machek 2017-12-21 14:59 ` Pavel Machek 2017-12-21 15:08 ` Michal Hocko 2017-12-21 15:08 ` Michal Hocko 2017-12-21 22:24 ` Andrew Morton 2017-12-21 22:24 ` Andrew Morton 2017-12-22 0:06 ` Michael Ellerman 2017-12-14 2:52 ` Jann Horn 2017-12-14 2:52 ` Jann Horn [not found] ` <CAG48ez0JZ3PVW3vgSXDmDijS+a_5bSX9qNuyggnsB6JTSkKngA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 2017-12-14 5:28 ` John Hubbard 2017-12-14 5:28 ` John Hubbard 2017-12-14 23:06 ` John Hubbard [not found] ` <b4fb7b3a-e53e-bf87-53c5-186751a14f4e-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org> 2017-12-14 23:10 ` Jann Horn 2017-12-14 23:10 ` Jann Horn [not found] ` <20171213092550.2774-1-mhocko-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> 2017-12-13 12:25 ` [PATCH v2 0/2] mm: introduce MAP_FIXED_SAFE Matthew Wilcox 2017-12-13 12:25 ` Matthew Wilcox 2017-12-13 12:34 ` Michal Hocko 2017-12-13 12:34 ` Michal Hocko 2017-12-13 17:13 ` Kees Cook 2017-12-13 17:13 ` Kees Cook 2017-12-15 9:02 ` Michael Ellerman 2017-12-15 9:02 ` Michael Ellerman 2017-12-14 0:32 ` Andrew Morton 2017-12-14 0:32 ` Andrew Morton 2017-12-14 1:35 ` David Goldblatt 2017-12-14 1:42 ` David Goldblatt 2017-12-14 1:42 ` David Goldblatt 2017-12-14 12:44 ` Edward Napierala 2017-12-14 13:15 ` Michal Hocko 2017-12-14 13:15 ` Michal Hocko 2017-12-14 14:54 ` Edward Napierala 2017-12-14 14:54 ` Edward Napierala 2017-12-19 12:40 ` David Laight 2017-12-19 12:40 ` David Laight 2017-12-19 12:46 ` Michal Hocko 2017-12-19 12:46 ` Michal Hocko
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=20171213093110.3550-1-mhocko@kernel.org \ --to=mhocko@kernel.org \ --cc=aarcange@redhat.com \ --cc=akpm@linux-foundation.org \ --cc=fweimer@redhat.com \ --cc=jhubbard@nvidia.com \ --cc=khalid.aziz@oracle.com \ --cc=linux-api@vger.kernel.org \ --cc=linux-arch@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mm@kvack.org \ --cc=linux@armlinux.org.uk \ --cc=mhocko@suse.com \ --cc=mpe@ellerman.id.au \ --cc=mtk.manpages@gmail.com \ --cc=willy@infradead.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: linkBe 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).