linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
To: Markus Trippelsdorf <markus@trippelsdorf.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [Kernel BUG] ext4 for v2.6.32 round II
Date: Thu, 1 Oct 2009 02:40:41 -0400	[thread overview]
Message-ID: <20091001064041.GV24383@mit.edu> (raw)
In-Reply-To: <20091001034716.GA2008@phenom2.trippelsdorf.de>

On Thu, Oct 01, 2009 at 05:47:16AM +0200, Markus Trippelsdorf wrote:
> On Wed, Sep 30, 2009 at 11:01:51PM -0400, Theodore Tso wrote:
> > Hi Markus, 
> > 
> > I'm pretty sure the following should fix your problems; can you
> > confirm?
> 
> Yes, everything is fine again.

Linus, can you pull from:

        git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git for_linus

This will pick up the fix to the problem Markus reported, plus some
old code that we had promised would be removed for 2.6.31.

    	      	     	      	       	       - Ted

Eric Sandeen (1):
      ext4: drop ext4dev compat

Theodore Ts'o (1):
      ext4: fix a BUG_ON crash by checking that page has buffers attached to it

 fs/ext4/Kconfig |   14 --------------
 fs/ext4/inode.c |   22 +++++++++++-----------
 fs/ext4/super.c |   31 -------------------------------
 3 files changed, 11 insertions(+), 56 deletions(-)

      reply	other threads:[~2009-10-01  6:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-30  5:25 [GIT PULL] ext4 for v2.6.32 round II Theodore Ts'o
2009-10-01  1:41 ` [Kernel BUG] " Markus Trippelsdorf
2009-10-01  1:57   ` Linus Torvalds
2009-10-01  2:15     ` Markus Trippelsdorf
2009-10-01  3:01       ` Theodore Tso
2009-10-01  3:47         ` Markus Trippelsdorf
2009-10-01  6:40           ` Theodore Tso [this message]

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=20091001064041.GV24383@mit.edu \
    --to=tytso@mit.edu \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markus@trippelsdorf.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).