linux-kernel - Re: [PATCH v2 0/4] fix several TLB batch races

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Tue, 1 Aug 2017 15:29:40 -0700
From:   Andrew Morton <akpm@...ux-foundation.org>
To:     Minchan Kim <minchan@...nel.org>
Cc:     linux-kernel@...r.kernel.org, linux-mm@...ck.org,
        kernel-team <kernel-team@....com>,
        Nadav Amit <nadav.amit@...il.com>,
        Mel Gorman <mgorman@...hsingularity.net>,
        Andrea Arcangeli <aarcange@...hat.com>
Subject: Re: [PATCH v2 0/4] fix several TLB batch races

On Tue,  1 Aug 2017 14:56:13 +0900 Minchan Kim <minchan@...nel.org> wrote:

> Nadav and Mel founded several subtle races caused by TLB batching.
> This patchset aims for solving thoses problems using embedding
> [inc|dec]_tlb_flush_pending to TLB batching API.
> With that, places to know TLB flush pending catch it up by
> using mm_tlb_flush_pending.
> 
> Each patch includes detailed description.
> 
> This patchset is based on v4.13-rc2-mmots-2017-07-28-16-10 +
> "[PATCH v5 0/3] mm: fixes of tlb_flush_pending races" from Nadav

Nadav is planning on doing a v4 of his patchset and it sounds like it
will be significantly different.

So I'll await that patch series.  Nadav, I think it would be best if
you were to integrate Minchan's patchset on top of yours and maintain the
whole set as a single series, please.  That way it all gets tested at
the same time and you're testing the hopefully-final result.  If that's
OK then please retain the various acks and reviewed-bys in the
changelogs.

And we'll need to figure out which kernel versions to fix.  Let's
target 4.13-rcX for now, and assess the feasibility and desirability of
backporting it all into -stable.