From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752706AbdHXLsi (ORCPT ); Thu, 24 Aug 2017 07:48:38 -0400 Received: from mx2.suse.de ([195.135.220.15]:35572 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751285AbdHXLsg (ORCPT ); Thu, 24 Aug 2017 07:48:36 -0400 Date: Thu, 24 Aug 2017 13:48:34 +0200 From: Michal Hocko To: Mark Rutland Cc: linux-kernel@vger.kernel.org, syzkaller@googlegroups.com, linux-mm@kvack.org, linux-fsdevel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Alexander Viro , Andrew Morton , Jan Kara , Ingo Molnar , Peter Zijlstra , Thomas Gleixner , Vlastimil Babka , will.deacon@arm.com Subject: Re: Intermittent memory corruption with v4.13-rc6+ and earlier Message-ID: <20170824114833.GH5943@dhcp22.suse.cz> References: <20170824113743.GA14737@leverpostej> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170824113743.GA14737@leverpostej> 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 On Thu 24-08-17 12:37:43, Mark Rutland wrote: > Hi, > > I'm chasing intermittent memory corruption bugs seen at least on rc5, > rc6, and yesterday's HEAD (98b9f8a4549909c6), on arm64. > > It looks like we make use of dangling references to a freed struct file, > which is caught by KASAN. Without KASAN, I see a number of other > intermittent issues that I suspect are the result of this memory > corruption. I've included an example splat below, complete with KASAN's > alloc/free traces at the end of this mail. Is it possible this is the same issue as the one fixed by http://lkml.kernel.org/r/20170823211408.31198-1-ebiggers3@gmail.com? -- Michal Hocko SUSE Labs