Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1031079AbdIZRbC (ORCPT ); Tue, 26 Sep 2017 13:31:02 -0400 Received: from foss.arm.com ([217.140.101.70]:36648 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1030992AbdIZRa7 (ORCPT ); Tue, 26 Sep 2017 13:30:59 -0400 Date: Tue, 26 Sep 2017 18:31:13 +0100 From: Will Deacon To: "Ruigrok, Richard" Cc: Yury Norov , linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: Re: ARM64: kernel panics in DABT in sys_msync path Message-ID: <20170926173112.GA16650@arm.com> References: <20170924213622.75e7r3k56tgxlezh@yury-thinkpad> <20170925105335.GA24042@arm.com> <20170925140240.vl5mvbce5lb37dxe@yury-thinkpad> <20170925190426.6prpcfn7lly26clm@yury-thinkpad> <20170926102324.GC8693@arm.com> <547ed590-3ab4-cc11-cbea-f587541d2b08@codeaurora.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <547ed590-3ab4-cc11-cbea-f587541d2b08@codeaurora.org> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1285 Lines: 30 Yury, Richard, On Tue, Sep 26, 2017 at 08:23:35AM -0600, Ruigrok, Richard wrote: > On 9/26/2017 4:23 AM, Will Deacon wrote: > > On Mon, Sep 25, 2017 at 01:54:57PM -0600, Ruigrok, Richard wrote: > >> I also found this issue with kernels from 4.11 through 4.13. In my tests, I > >> found that it reproduces only with 4K page and Transparent Huge Pages. With 64K > >> page I was not able to reproduce. RH also reported it here: https:// > >> bugzilla.redhat.com/show_bug.cgi?id=1491504 Linaro reported on the RPK kernel > >> (4.12) on Centriq2400 and ThunderX > >> > >> > >> https://bugs.linaro.org/show_bug.cgi?id=3191 > >> > >> https://bugs.linaro.org/show_bug.cgi?id=3068. > > These two aren't the same bug (that's a forward progress issue that we're > > currently working on). I don't have permission to look at the redhat one, > > but is it just an RCU stall or actually the Oops reported by Yury? > > > >> I was able to bisect down to a specific commit. > > I think we're chasing two different things here, so not sure I trust the > > bisect! > > > The RCU stall is side effect.? The issue I'm seeing has the same stack > trace and same stimulus (rwtest).? Following are the details. FWIW, I think I've worked out what's going on here and I should have a patch tomorrow. Will