On Tue, Dec 5, 2017 at 6:58 AM, Michal Hocko <[email protected]> wrote:
>
> This all is nice but tlb_gather users are not aware of that and this can
> actually cause some real problems. E.g. the oom_reaper tries to reap the
> whole address space but it might race with threads accessing the memory [1].
> It is possible that soft-dirty handling might suffer from the same
> problem [2] as soon as it starts supporting the feature.
So we fixed the oom reaper to just do proper TLB invalidates in commit
687cb0884a71 ("mm, oom_reaper: gather each vma to prevent leaking TLB
entry").
So now "fullmm" should be the expected "exit" case, and it all should
be unambiguous.
Do we really have any reason to apply this patch any more?
Linus
