From: stsp <stsp2@yandex.ru>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: linux-mm@kvack.org, Brian Geffon <bgeffon@google.com>,
Li Xinhai <lixinhai.lxh@gmail.com>,
Dmitry Safonov <0x7f454c46@gmail.com>
Subject: Re: MREMAP_DONTUNMAP corrupts initial mapping
Date: Thu, 30 Mar 2023 19:45:14 +0500 [thread overview]
Message-ID: <38c80313-ba1c-092c-ae31-f58fe6ffa82c@yandex.ru> (raw)
In-Reply-To: <aee53ac3-6d25-5009-7416-3f7c5fe1f989@yandex.ru>
Add a few CCs.
30.03.2023 17:38, stsp пишет:
> Hello.
>
> Attached is a small test-case that
> demonstrates the problem.
> The problem happens if you change
> some data in a file-backed private
> mapping and then use mremap on
> it with MREMAP_DONTUNMAP flag.
> The result is:
> - destination copy is valid
> - source copy restored from the original file
>
> So the 2 copies do not match.
next parent reply other threads:[~2023-03-30 14:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <aee53ac3-6d25-5009-7416-3f7c5fe1f989@yandex.ru>
2023-03-30 14:45 ` stsp [this message]
2023-03-30 18:42 ` Lorenzo Stoakes
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=38c80313-ba1c-092c-ae31-f58fe6ffa82c@yandex.ru \
--to=stsp2@yandex.ru \
--cc=0x7f454c46@gmail.com \
--cc=bgeffon@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lixinhai.lxh@gmail.com \
/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