From: Valerie Aurora Henson <vaurora@redhat.com>
To: Nick Dokos <nicholas.dokos@hp.com>
Cc: "Theodore Ts'o" <tytso@mit.edu>, linux-ext4@vger.kernel.org
Subject: Re: [PATCH 1/5][64-BIT] ext2fs_block_alloc_stats2: fix size comparison for 64-bit compatibility.
Date: Wed, 15 Apr 2009 15:53:56 -0400 [thread overview]
Message-ID: <20090415195356.GC1668@shell> (raw)
In-Reply-To: <11636.1239227165@alphaville.usa.hp.com>
On Wed, Apr 08, 2009 at 05:46:05PM -0400, Nick Dokos wrote:
> The block number comparison in ext2fs_block_alloc_stats2() is invalid
> for 64-bit filesystems: it compares the block number to the low
> 32-bits of the blocks_count in the superblock. That caused the journal
> file for a 32TiB filesystem to be malformed and the resulting filesystem
> could not be mounted.
>
> The function now uses ext2fs_blocks_count() [from blknum.c] to calculate
> the number of blocks.
>
> With this change, the journal looks sane and the filesystem could be
> mounted.
>
> Signed-off-by: Nick Dokos <nicholas.dokos@hp.com>
Signed-off-by: Valerie Aurora (Henson) <vaurora@redhat.com>
> ---
> lib/ext2fs/alloc_stats.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/lib/ext2fs/alloc_stats.c b/lib/ext2fs/alloc_stats.c
> index 7895aee..f0c5a64 100644
> --- a/lib/ext2fs/alloc_stats.c
> +++ b/lib/ext2fs/alloc_stats.c
> @@ -65,7 +65,7 @@ void ext2fs_block_alloc_stats2(ext2_filsys fs, blk64_t blk, int inuse)
> int group = ext2fs_group_of_blk2(fs, blk);
>
> #ifndef OMIT_COM_ERR
> - if (blk >= fs->super->s_blocks_count) {
> + if (blk >= ext2fs_blocks_count(fs->super)) {
> com_err("ext2fs_block_alloc_stats2", 0,
> "Illegal block number: %lu", blk);
> return;
> --
> 1.6.0.6
>
prev parent reply other threads:[~2009-04-15 19:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-08 21:46 [PATCH 1/5][64-BIT] ext2fs_block_alloc_stats2: fix size comparison for 64-bit compatibility Nick Dokos
2009-04-15 19:53 ` Valerie Aurora Henson [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=20090415195356.GC1668@shell \
--to=vaurora@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=nicholas.dokos@hp.com \
--cc=tytso@mit.edu \
/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).