From: Mike Kravetz <mike.kravetz@oracle.com>
To: Florian Weimer <fweimer@redhat.com>, mtk.manpages@gmail.com
Cc: linux-man@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-api@vger.kernel.org, Michal Hocko <mhocko@suse.com>,
Andrea Arcangeli <aarcange@redhat.com>,
"Kirill A . Shutemov" <kirill.shutemov@linux.intel.com>,
Vlastimil Babka <vbabka@suse.cz>,
Anshuman Khandual <khandual@linux.vnet.ibm.com>,
linux-mm@kvack.org
Subject: Re: [patch] mremap.2: Add description of old_size == 0 functionality
Date: Mon, 18 Sep 2017 10:11:44 -0700 [thread overview]
Message-ID: <ee87215d-9704-7269-4ec1-226f2e32a751@oracle.com> (raw)
In-Reply-To: <fb013ae6-6f47-248b-db8b-a0abae530377@redhat.com>
On 09/18/2017 06:45 AM, Florian Weimer wrote:
> On 09/15/2017 11:53 PM, Mike Kravetz wrote:
>> +If the value of \fIold_size\fP is zero, and \fIold_address\fP refers to
>> +a private anonymous mapping, then
>> +.BR mremap ()
>> +will create a new mapping of the same pages. \fInew_size\fP
>> +will be the size of the new mapping and the location of the new mapping
>> +may be specified with \fInew_address\fP, see the description of
>> +.B MREMAP_FIXED
>> +below. If a new mapping is requested via this method, then the
>> +.B MREMAP_MAYMOVE
>> +flag must also be specified. This functionality is deprecated, and no
>> +new code should be written to use this feature. A better method of
>> +obtaining multiple mappings of the same private anonymous memory is via the
>> +.BR memfd_create()
>> +system call.
>
> Is there any particular reason to deprecate this?
>
> In glibc, we cannot use memfd_create and keep the file descriptor around because the application can close descriptors beneath us.
>
> (We might want to use alias mappings to avoid run-time code generation for PLT-less LD_AUDIT interceptors.)
>
Hi Florian,
When I brought up this mremap 'duplicate mapping' functionality on the mm
mail list, most developers were surprised. It seems this functionality exists
mostly 'by chance', and it was not really designed. It certainly was never
documented. There were suggestions to remove the functionality, which led
to my claim that it was being deprecated. However, in hindsight that may
have been too strong.
I can drop this wording, but would still like to suggest memfd_create as
the preferred method of creating duplicate mappings. It would be good if
others on Cc: could comment as well.
Just curious, does glibc make use of this today? Or, is this just something
that you think may be useful.
--
Mike Kravetz
--
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>
next prev parent reply other threads:[~2017-09-18 17:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170915213745.6821-1-mike.kravetz@oracle.com>
2017-09-15 21:53 ` Mike Kravetz
2017-09-18 13:45 ` Florian Weimer
2017-09-18 17:11 ` Mike Kravetz [this message]
2017-09-19 12:11 ` Florian Weimer
2017-09-19 21:42 ` [patch v2] " Mike Kravetz
2017-09-20 7:25 ` Michael Kerrisk (man-pages)
2017-09-25 12:36 ` Michal Hocko
2017-09-25 12:40 ` Michael Kerrisk (man-pages)
2017-09-25 16:33 ` Mike Kravetz
2017-09-25 19:26 ` Michael Kerrisk (man-pages)
2017-09-25 12:35 ` [patch] " Michal Hocko
2017-09-25 12:40 ` Florian Weimer
2017-09-25 12:52 ` Michal Hocko
2017-09-25 13:16 ` Florian Weimer
2017-09-25 14:52 ` Michal Hocko
2017-09-25 14:54 ` Florian Weimer
2017-09-18 1:52 ` Jann Horn
2017-09-18 17:19 ` Mike Kravetz
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=ee87215d-9704-7269-4ec1-226f2e32a751@oracle.com \
--to=mike.kravetz@oracle.com \
--cc=aarcange@redhat.com \
--cc=fweimer@redhat.com \
--cc=khandual@linux.vnet.ibm.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=mtk.manpages@gmail.com \
--cc=vbabka@suse.cz \
/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