[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f0340108-a1ce-85cd-23dd-790848603b37@suse.cz>
Date: Tue, 25 Feb 2020 14:51:34 +0100
From: Vlastimil Babka <vbabka@...e.cz>
To: Brian Geffon <bgeffon@...gle.com>,
Andrew Morton <akpm@...ux-foundation.org>
Cc: "Michael S . Tsirkin" <mst@...hat.com>,
Arnd Bergmann <arnd@...db.de>, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, linux-api@...r.kernel.org,
Andy Lutomirski <luto@...capital.net>,
Will Deacon <will@...nel.org>,
Andrea Arcangeli <aarcange@...hat.com>,
Sonny Rao <sonnyrao@...gle.com>,
Minchan Kim <minchan@...nel.org>,
Joel Fernandes <joel@...lfernandes.org>,
Yu Zhao <yuzhao@...gle.com>,
Jesse Barnes <jsbarnes@...gle.com>,
Florian Weimer <fweimer@...hat.com>,
"Kirill A . Shutemov" <kirill@...temov.name>,
mtk.manpages@...il.com, linux-man@...r.kernel.org
Subject: Re: [PATCH v7] mremap.2: Add information for MREMAP_DONTUNMAP.
On 2/21/20 6:42 PM, Brian Geffon wrote:
> @@ -209,10 +227,20 @@ flag was not specified.
> .RE
> .TP
> .B ENOMEM
> +Not enough memory was available to complete the operation.
> +Possible causes are:
> +.RS
> +.IP * 3
> The memory area cannot be expanded at the current virtual address, and the
> .B MREMAP_MAYMOVE
> flag is not set in \fIflags\fP.
> Or, there is not enough (virtual) memory available.
> +.IP *
> +.B MREMAP_DONTUNMAP
> +was used without
> +.B MREMAP_FIXED
> +causing a new mapping to be created that would exceed the virtual memory available or it would exceed the maximum number of allowed mappings.
So this can also result with MREMAP_FIXED, no?
> +.RE
> .SH CONFORMING TO
> This call is Linux-specific, and should not be used in programs
> intended to be portable.
>
Powered by blists - more mailing lists