From: Theodore Tso <tytso@mit.edu>
To: Eric Sandeen <sandeen@redhat.com>
Cc: Thiemo Nagel <thiemo.nagel@ph.tum.de>,
Ext4 Developers List <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] fix bogus BUG_ONs in in mballoc code
Date: Thu, 12 Mar 2009 21:09:40 -0400 [thread overview]
Message-ID: <20090313010940.GO17104@mit.edu> (raw)
In-Reply-To: <49B958A1.6060805@redhat.com>
On Thu, Mar 12, 2009 at 01:46:57PM -0500, Eric Sandeen wrote:
> Thiemo Nagel reported that:
>
> # dd if=/dev/zero of=image.ext4 bs=1M count=2
> # mkfs.ext4 -v -F -b 1024 -m 0 -g 512 -G 4 -I 128 -N 1 \
> -O large_file,dir_index,flex_bg,extent,sparse_super image.ext4
> # mount -o loop image.ext4 mnt/
> # dd if=/dev/zero of=mnt/file
>
> oopsed, with a BUG_ON in ext4_mb_normalize_request because
> size == EXT4_BLOCKS_PER_GROUP
>
> It appears to me (esp. after talking to Andreas) that the BUG_ON
> is bogus; a request of exactly EXT4_BLOCKS_PER_GROUP should
> be allowed, though larger sizes do indicate a problem.
>
> Fix that an another (apparently rare) codepath with a similar check.
Hmm.... is this at all likely to happen with a standard ext4
filesystem parameters? Or was this triggered because of the
artifially set -g 512 parameter? The question is whether we should
try pushing this to Linus at this point, or let this wait until the
merge window opens.
Opinions?
= Ted
<
next prev parent reply other threads:[~2009-03-13 1:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-12 16:54 BUG at fs/ext4/mballoc.c:3295 Thiemo Nagel
2009-03-12 17:07 ` Eric Sandeen
2009-03-12 17:13 ` Thiemo Nagel
2009-03-12 17:16 ` Eric Sandeen
2009-03-12 18:46 ` [PATCH] fix bogus BUG_ONs in in mballoc code Eric Sandeen
2009-03-13 0:38 ` Theodore Tso
2009-03-13 11:09 ` Andreas Dilger
2009-03-13 1:09 ` Theodore Tso [this message]
2009-03-13 2:08 ` Eric Sandeen
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=20090313010940.GO17104@mit.edu \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.com \
--cc=thiemo.nagel@ph.tum.de \
/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).