From: Michal Hocko <mhocko@kernel.org>
To: Minchan Kim <minchan@kernel.org>
Cc: Wang Nan <wangnan0@huawei.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
will.deacon@arm.com, Bob Liu <liubo95@huawei.com>,
Andrew Morton <akpm@linux-foundation.org>,
David Rientjes <rientjes@google.com>,
Ingo Molnar <mingo@kernel.org>, Roman Gushchin <guro@fb.com>,
Konstantin Khlebnikov <khlebnikov@yandex-team.ru>,
Andrea Arcangeli <aarcange@redhat.com>
Subject: [PATCH] arch, mm: introduce arch_tlb_gather_mmu_lazy (was: Re: [RESEND PATCH] mm, oom_reaper: gather each vma to prevent) leaking TLB entry
Date: Fri, 10 Nov 2017 13:26:35 +0100 [thread overview]
Message-ID: <20171110122635.q26xdxytgdfjy5q3@dhcp22.suse.cz> (raw)
In-Reply-To: <20171110101529.op6yaxtdke2p4bsh@dhcp22.suse.cz>
On Fri 10-11-17 11:15:29, Michal Hocko wrote:
> On Fri 10-11-17 09:19:33, Minchan Kim wrote:
> > On Tue, Nov 07, 2017 at 09:54:53AM +0000, Wang Nan wrote:
> > > tlb_gather_mmu(&tlb, mm, 0, -1) means gathering the whole virtual memory
> > > space. In this case, tlb->fullmm is true. Some archs like arm64 doesn't
> > > flush TLB when tlb->fullmm is true:
> > >
> > > commit 5a7862e83000 ("arm64: tlbflush: avoid flushing when fullmm == 1").
> > >
> > > Which makes leaking of tlb entries.
> >
> > That means soft-dirty which has used tlb_gather_mmu with fullmm could be
> > broken via losing write-protection bit once it supports arm64 in future?
> >
> > If so, it would be better to use TASK_SIZE rather than -1 in tlb_gather_mmu.
> > Of course, it's a off-topic.
>
> I wouldn't play tricks like that. And maybe the API itself could be more
> explicit. E.g. add a lazy parameter which would allow arch specific code
> to not flush if it is sure that nobody can actually stumble over missed
> flush. E.g. the following?
This one has a changelog and even compiles on my crosscompile test
---
next prev parent reply other threads:[~2017-11-10 12:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-07 9:54 [RESEND PATCH] mm, oom_reaper: gather each vma to prevent " Wang Nan
2017-11-07 10:09 ` Michal Hocko
2017-11-10 0:19 ` Minchan Kim
2017-11-10 10:15 ` Michal Hocko
2017-11-10 12:26 ` Michal Hocko [this message]
2017-11-13 0:28 ` [PATCH] arch, mm: introduce arch_tlb_gather_mmu_lazy (was: Re: [RESEND PATCH] mm, oom_reaper: gather each vma to prevent) " Minchan Kim
2017-11-13 9:51 ` Michal Hocko
2017-11-14 1:45 ` Minchan Kim
2017-11-14 7:21 ` Michal Hocko
2017-11-15 0:12 ` Minchan Kim
2017-11-15 8:14 ` Michal Hocko
2017-11-16 0:44 ` Minchan Kim
2017-11-16 9:19 ` Michal Hocko
2017-11-15 17:33 ` Will Deacon
2017-11-16 9:20 ` Michal Hocko
2017-11-20 14:24 ` Will Deacon
2017-11-20 16:04 ` [PATCH] arch, mm: introduce arch_tlb_gather_mmu_lazy Michal Hocko
2017-11-22 19:30 ` Will Deacon
2017-11-23 6:18 ` Minchan Kim
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=20171110122635.q26xdxytgdfjy5q3@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=guro@fb.com \
--cc=khlebnikov@yandex-team.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liubo95@huawei.com \
--cc=minchan@kernel.org \
--cc=mingo@kernel.org \
--cc=rientjes@google.com \
--cc=wangnan0@huawei.com \
--cc=will.deacon@arm.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