From: Michal Hocko <mhocko@kernel.org>
To: Li Xinhai <lixinhai.lxh@gmail.com>
Cc: akpm <akpm@linux-foundation.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [PATCH 0/3] mm: Fix misuse of parent anon_vma in dup_mmap path
Date: Tue, 21 Apr 2020 09:26:59 +0200 [thread overview]
Message-ID: <20200421072659.GC27314@dhcp22.suse.cz> (raw)
In-Reply-To: <2020042111530118847536@gmail.com>
On Tue 21-04-20 11:53:02, Li Xinhai wrote:
> On 2020-04-20 at 20:06 Michal Hocko wrote:
[...]
> > Because from my current understanding it would
> >only make WIPEONFORK vmas rmap walks less efficient. Or is there any
> >other functional issue?
> #1 issue is for case WIPEONFORK, #2 issue for all other cases of anonymous VMA dup
> (i.e., when parent vmas is currently sharing anon_vma among themself, child vma will
> share its parent vma's anon_vma).
OK, it was not really clear to me that also !WIPEONFORK vmas are
affected. Thanks for the clarification.
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2020-04-21 7:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-08 8:35 [PATCH 0/3] mm: Fix misuse of parent anon_vma in dup_mmap path Li Xinhai
2020-02-08 8:35 ` [PATCH 1/3] mm: don't prepare anon_vma if vma has VM_WIPEONFORK Li Xinhai
2020-02-08 8:53 ` Li Xinhai
2020-04-02 13:45 ` Kirill A. Shutemov
2020-02-08 8:35 ` [PATCH 2/3] Revert "mm/rmap.c: reuse mergeable anon_vma as parent when fork" Li Xinhai
2020-04-02 13:59 ` Kirill A. Shutemov
2020-04-03 3:08 ` Li Xinhai
2020-04-05 1:26 ` Li Xinhai
2020-02-08 8:35 ` [PATCH 3/3] mm: set vm_next and vm_prev to NULL in vm_area_dup() Li Xinhai
2020-04-02 14:07 ` Kirill A. Shutemov
2020-02-10 0:52 ` [PATCH 0/3] mm: Fix misuse of parent anon_vma in dup_mmap path Andrew Morton
2020-02-10 2:15 ` Li Xinhai
2020-04-20 12:06 ` Michal Hocko
2020-04-21 3:53 ` Li Xinhai
2020-04-21 7:26 ` Michal Hocko [this message]
2020-04-02 1:25 ` Andrew Morton
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=20200421072659.GC27314@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).