From: Pavel Emelyanov <xemul@parallels.com>
To: "Kirill A. Shutemov" <kirill@shutemov.name>
Cc: Linux MM <linux-mm@kvack.org>, Hugh Dickins <hughd@google.com>
Subject: Re: Unexpected mremap + shared anon mapping behavior
Date: Fri, 08 Mar 2013 13:04:22 +0400 [thread overview]
Message-ID: <5139A996.4070303@parallels.com> (raw)
In-Reply-To: <20130308085301.GB4411@shutemov.name>
>> So, the question is -- what should the mremap() behavior be for shared anonymous mappings?
>> Should it truncate the file to match the grown-up vma length? If yes, should it also
>> truncate it if we mremap() the mapping to the smaller size?
>
> I think the answer is 'no' for both cases. It's ABI change.
>
> Should we introduce mtruncate() syscall which will truncate backing fail
> in both cases? ;)
>
If we don't touch kernel mremap, then mtruncate can be done in glibc via /proc/pid/map_files :)
Thanks,
Pavel
--
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:[~2013-03-08 9:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-08 8:27 Unexpected mremap + shared anon mapping behavior Pavel Emelyanov
2013-03-08 8:53 ` Kirill A. Shutemov
2013-03-08 9:04 ` Pavel Emelyanov [this message]
2013-03-12 2:53 ` Hugh Dickins
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=5139A996.4070303@parallels.com \
--to=xemul@parallels.com \
--cc=hughd@google.com \
--cc=kirill@shutemov.name \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.