Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754088AbcLALad (ORCPT ); Thu, 1 Dec 2016 06:30:33 -0500 Received: from foss.arm.com ([217.140.101.70]:40744 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750775AbcLALac (ORCPT ); Thu, 1 Dec 2016 06:30:32 -0500 Date: Thu, 1 Dec 2016 11:30:32 +0000 From: Will Deacon To: Ming Lei Cc: Linux FS Devel , Alexander Viro , Jeff Layton , "J. Bruce Fields" , Catalin Marinas , Linux Kernel Mailing List , linux-arm-kernel Subject: Re: [bug report v4.8] fs/locks.c: kernel oops during posix lock stress test Message-ID: <20161201113031.GB5813@arm.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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: 1108 Lines: 27 On Mon, Nov 28, 2016 at 11:10:14AM +0800, Ming Lei wrote: > When I run stress-ng via the following steps on one ARM64 dual > socket system(Cavium Thunder), the kernel oops[1] can often be > triggered after running the stress test for several hours(sometimes > it may take longer): > > - git clone git://kernel.ubuntu.com/cking/stress-ng.git > - apply the attachment patch which just makes the posix file > lock stress test more aggressive > - run the test via '~/git/stress-ng$./stress-ng --lockf 128 --aggressive' > > > From the oops log, looks one garbage file_lock node is got > from the linked list of 'ctx->flc_posix' when the issue happens. > > BTW, the issue isn't observed on single socket Cavium Thunder yet, > and the same issue can be seen on Ubuntu Xenial(v4.4 based kernel) > too. FWIW, I've been running this on Seattle for 24 hours with your patch applied and not seen any problems yet. That said, Thomas did just fix an rt_mutex race which only seemed to pop up on Thunder, so you could give those patches a try. https://lkml.kernel.org/r/20161130205431.629977871@linutronix.de Will