Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1755304AbbF0OHw (ORCPT <rfc822;w@1wt.eu>);
	Sat, 27 Jun 2015 10:07:52 -0400
Received: from imap.thunk.org ([74.207.234.97]:57851 "EHLO imap.thunk.org"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1751641AbbF0OHp (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Sat, 27 Jun 2015 10:07:45 -0400
Date: Sat, 27 Jun 2015 10:07:43 -0400
From: "Theodore Ts'o" <tytso@mit.edu>
To: Linus Torvalds <torvalds@linux-foundation.org>, Jan Kara <jack@suse.cz>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        "linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Re: [GIT PULL] ext4 changes for 4.2-rc1
Message-ID: <20150627140743.GF474@thunk.org>
Mail-Followup-To: Theodore Ts'o <tytso@mit.edu>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Jan Kara <jack@suse.cz>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
References: <20150625034626.GA21682@thunk.org>
 <CA+55aFwXgrcfqN2f7R8PbcDr9yiWXv4cicKmKfQFxR_KsHaiwQ@mail.gmail.com>
 <20150627040237.GC474@thunk.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20150627040237.GC474@thunk.org>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: tytso@thunk.org
X-SA-Exim-Scanned: No (on imap.thunk.org); SAEximRunCond expanded to false
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 1112
Lines: 22

On Sat, Jun 27, 2015 at 12:02:37AM -0400, Theodore Ts'o wrote:
> 
> I would tend to agree.  The weird thing though is that I haven't seen
> this problem myself, despite running multiple regression tests before
> I sent the pull request, as well as running it on my laptop and doing
> kernel compiles with make -j16 and reading e-mail (I'm typing this
> e-mail on a 4.1 kernel merged with the ext4 patches for this merge
> window, so I have this commit running in my development laptop, and it
> hasn't triggered for me).

Update: I've been able to reproduce the crash using a post merge
kernel (of course, I had to use CONFIG_SLUB since CONFIG_SLAB is
busted) a single time.  Unfortunately, I've not been able to reproduce
it reliably so I can't speak to whether reverting 2143c1965a76 will
fix things.  But it does seem very likely.

    	     	    	      	   - Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/