[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <b686a7e397b992cf7a32b2e5e7c3503919a8c717.camel@surriel.com>
Date: Fri, 07 Sep 2018 10:28:05 -0400
From: Rik van Riel <riel@...riel.com>
To: Will Deacon <will.deacon@....com>
Cc: Nicholas Piggin <npiggin@...il.com>,
Peter Zijlstra <peterz@...radead.org>,
torvalds@...ux-foundation.org, luto@...nel.org, x86@...nel.org,
bp@...en8.de, jannh@...gle.com, ascannell@...gle.com,
dave.hansen@...el.com, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, David Miller <davem@...emloft.net>,
Martin Schwidefsky <schwidefsky@...ibm.com>,
Michael Ellerman <mpe@...erman.id.au>,
linux-arch@...r.kernel.org
Subject: Re: [RFC PATCH 1/2] mm: move tlb_table_flush to tlb_flush_mmu_free
On Fri, 2018-09-07 at 14:44 +0100, Will Deacon wrote:
> On Thu, Sep 06, 2018 at 04:29:59PM -0400, Rik van Riel wrote:
> > On Thu, 2018-08-23 at 18:47 +1000, Nicholas Piggin wrote:
> > > There is no need to call this from tlb_flush_mmu_tlbonly, it
> > > logically belongs with tlb_flush_mmu_free. This allows some
> > > code consolidation with a subsequent fix.
> > >
> > > Signed-off-by: Nicholas Piggin <npiggin@...il.com>
> >
> > Reviewed-by: Rik van Riel <riel@...riel.com>
> >
> > This patch also fixes an infinite recursion bug
> > with CONFIG_HAVE_RCU_TABLE_FREE enabled, which
> > has this call trace:
> >
> > tlb_table_flush
> > -> tlb_table_invalidate
> > -> tlb_flush_mmu_tlbonly
> > -> tlb_table_flush
> > -> ... (infinite recursion)
> >
> > This should probably be applied sooner rather than
> > later.
>
> It's already in mainline with a cc stable afaict.
Sure enough, it is.
I guess I have too many kernel trees on this
system, and was looking at the wrong one somehow.
--
All Rights Reversed.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists