From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com ([209.132.183.28]:17600 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752302Ab3F0PTc (ORCPT ); Thu, 27 Jun 2013 11:19:32 -0400 Date: Thu, 27 Jun 2013 11:19:22 -0400 From: Dave Jones To: Chris Mason Cc: Linux Kernel , linux-btrfs@vger.kernel.org Subject: Re: btrfs triggered lockdep WARN. Message-ID: <20130627151922.GA1438@redhat.com> References: <20130627145824.GA21540@redhat.com> <20130627150130.14981.39849@localhost.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <20130627150130.14981.39849@localhost.localdomain> Sender: linux-btrfs-owner@vger.kernel.org List-ID: On Thu, Jun 27, 2013 at 11:01:30AM -0400, Chris Mason wrote: > Quoting Dave Jones (2013-06-27 10:58:24) > > Another bug caused by this script. https://github.com/kernelslacker/io-tests/blob/master/setup.sh > > I'm still struggling to reproduce that one here. I've tried every > variation I can think of but I'll try again. Note that this is a different trace to the other post about that script. > I really hope you don't already have CONFIG_DEBUG_PAGE_ALLOC turned on, > maybe it will catch this? I do. Though given this is lockdep complaining about what looks like memory corruption, it's probably not related. Dave