linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: Eric Whitney <enwlinux@gmail.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH] ext4: fix bigalloc regression
Date: Mon, 6 Jan 2014 15:07:05 -0500	[thread overview]
Message-ID: <20140106200705.GD28490@thunk.org> (raw)
In-Reply-To: <20140106184619.GB2211@wallace>

On Mon, Jan 06, 2014 at 01:46:19PM -0500, Eric Whitney wrote:
> Commit f5a44db5d2 introduced a regression on filesystems created with
> the bigalloc feature (cluster size > blocksize).  It causes xfstests
> generic/006 and /013 to fail with an unexpected JBD2 failure and
> transaction abort that leaves the test file system in a read only state.
> Other xfstests run on bigalloc file systems are likely to fail as well.
> 
> The cause is the accidental use of a cluster mask where a cluster
> offset was needed in ext4_ext_map_blocks().
> 
> Signed-off-by: Eric Whitney <enwlinux@gmail.com>

Thanks, applied.

					- Ted

      reply	other threads:[~2014-01-06 20:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-06 18:46 [PATCH] ext4: fix bigalloc regression Eric Whitney
2014-01-06 20:07 ` Theodore Ts'o [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=20140106200705.GD28490@thunk.org \
    --to=tytso@mit.edu \
    --cc=enwlinux@gmail.com \
    --cc=linux-ext4@vger.kernel.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).