All of lore.kernel.org
 help / color / mirror / Atom feed
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
Date: Sat, 27 Jun 2015 10:07:43 -0400	[thread overview]
Message-ID: <20150627140743.GF474@thunk.org> (raw)
In-Reply-To: <20150627040237.GC474@thunk.org>

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

  reply	other threads:[~2015-06-27 14:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-25  3:46 [GIT PULL] ext4 changes for 4.2-rc1 Theodore Ts'o
2015-06-25  4:54 ` Theodore Ts'o
2015-06-26  2:19   ` Theodore Ts'o
2015-06-25 15:37 ` Holger Hoffstätte
2015-06-27  3:05 ` Linus Torvalds
2015-06-27  4:02   ` Theodore Ts'o
2015-06-27 14:07     ` Theodore Ts'o [this message]
2015-06-29  8:27       ` Jan Kara
2015-06-29  9:04       ` Jan Kara
2015-06-29 20:49         ` Theodore Ts'o
2015-06-29 12:31   ` Ming Lei

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150627140743.GF474@thunk.org \
    --to=tytso@mit.edu \
    --cc=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.