From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751965Ab3KRRNS (ORCPT ); Mon, 18 Nov 2013 12:13:18 -0500 Received: from mail-ee0-f53.google.com ([74.125.83.53]:51627 "EHLO mail-ee0-f53.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751375Ab3KRRNO (ORCPT ); Mon, 18 Nov 2013 12:13:14 -0500 Date: Mon, 18 Nov 2013 18:13:10 +0100 From: Ingo Molnar To: Vince Weaver Cc: Peter Zijlstra , LKML , Paul Mackerras , Arnaldo Carvalho de Melo , tytso@mit.edu, adilger.kernel@dilger.ca Subject: Re: perf bug: bad page map Message-ID: <20131118171310.GA28736@gmail.com> References: <20131118151746.GC10022@twins.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Vince Weaver wrote: > On Mon, 18 Nov 2013, Peter Zijlstra wrote: > > > On Fri, Nov 15, 2013 at 01:04:23PM -0500, Vince Weaver wrote: > > > > > > (figured out the minicom issue). > > > > > > Anyway while trying to reproduce the last bug I instead got this with > > > the perf_fuzzer. > > > > > > Is it worth continuing to run and report these issues? I'm losing track > > > of all the open bugs. > > > > This is looks like ext4. Not entirely sure how perf ties into this. > > It's believable the filesystem could have issues (it's a fuzzer > machine, so it's had 100+ unclean shutdowns on an SSD drive in the > past few months) but as far as I know there shouldn't have been any > filesystem accesses happening at all when the bug triggered. > > I thought it might be perf related due to the perf references in the > backtrace (and since it was being perf-fuzzed at the time). Maybe the connection is that ext4 has lots of tracepoints? Thanks, Ingo