From: "Li Xinhai" <lixinhai.lxh@gmail.com>
To: khlebnikov <khlebnikov@yandex-team.ru>,
richardw.yang <richardw.yang@linux.intel.com>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
akpm <akpm@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Rik van Riel" <riel@redhat.com>,
kirill.shutemov <kirill.shutemov@linux.intel.com>
Subject: Re: [PATCH v2 1/2] mm/rmap: fix and simplify reusing mergeable anon_vma as parent when fork
Date: Tue, 14 Jan 2020 22:42:52 +0800 [thread overview]
Message-ID: <2020011422424965556826@gmail.com> (raw)
In-Reply-To: 1cf002fa-a3cb-bcef-57dc-ac9c09dcf2eb@yandex-team.ru
On 2020-01-13 at 19:07 Konstantin Khlebnikov wrote:
>
>Because I want to keep both heuristics.
>This seems most sane way of interaction between them.
>
>Unfortunately even this patch is slightly broken.
>Condition prev->anon_vma->parent == pvma->anon_vma doesn't guarantee that
>prev vma has the same set of anon-vmas like current vma.
>I.e. anon_vma_clone(vma, prev) might be not enough for keeping connectivity.
New patch is required?
It is necessary to call anon_vma_clone(vma, pvma) to link all anon_vma which
currently linked by pvma, then link the prev->anon_vma to vma. By this way,
connectivity of vma should be maintained, right?
>Building such case isn't trivial job but I see nothing that could prevent it.
>
next prev parent reply other threads:[~2020-01-14 14:42 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-07 10:19 [PATCH v2 1/2] mm/rmap: fix and simplify reusing mergeable anon_vma as parent when fork Konstantin Khlebnikov
2020-01-07 10:19 ` [PATCH v2 2/2] kernel/fork: set VMA's mm/prev/next right after vm_area_dup in dup_mmap Konstantin Khlebnikov
2020-01-07 14:22 ` lixinhai.lxh
2020-01-07 13:35 ` [PATCH v2 1/2] mm/rmap: fix and simplify reusing mergeable anon_vma as parent when fork lixinhai.lxh
2020-01-08 2:32 ` Wei Yang
2020-01-08 6:42 ` lixinhai.lxh
2020-01-08 10:40 ` Konstantin Khlebnikov
2020-01-09 2:52 ` Wei Yang
2020-01-09 8:54 ` Konstantin Khlebnikov
2020-01-10 2:30 ` Wei Yang
2020-01-10 3:23 ` Li Xinhai
2020-01-10 5:34 ` Wei Yang
2020-01-10 8:11 ` Konstantin Khlebnikov
2020-01-11 22:38 ` Wei Yang
2020-01-12 9:55 ` Konstantin Khlebnikov
2020-01-13 0:33 ` Wei Yang
2020-01-13 11:07 ` Konstantin Khlebnikov
2020-01-14 2:09 ` Wei Yang
2020-01-14 14:42 ` Li Xinhai [this message]
2020-01-15 1:20 ` Wei Yang
2020-01-18 8:04 ` Konstantin Khlebnikov
2020-01-18 14:00 ` Wei Yang
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=2020011422424965556826@gmail.com \
--to=lixinhai.lxh@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=khlebnikov@yandex-team.ru \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=richardw.yang@linux.intel.com \
--cc=riel@redhat.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;
as well as URLs for NNTP newsgroup(s).