From: Theodore Ts'o <tytso@mit.edu>
To: "Lukáš Czerner" <lczerner@redhat.com>
Cc: Ext4 Developers List <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH 1/2] libext2fs: fix alloc_allocate_group_table() if the flexbg_offset wraps
Date: Tue, 29 Apr 2014 22:34:14 -0400 [thread overview]
Message-ID: <20140430023414.GC6714@thunk.org> (raw)
In-Reply-To: <alpine.LFD.2.00.1404291259500.2183@localhost.localdomain>
On Tue, Apr 29, 2014 at 01:02:07PM +0200, Lukáš Czerner wrote:
>
> Not sure about this, but I just wonder whether this would work with
> bigalloc file system as well since it is true that we're testing
> blocks in this condition but in ext2fs_test_block_bitmap_range2()
> we're searching for a free cluster.
No, we're fine because the bitmap functions takes block numbers as
arguments, not cluster numbers. (The bitmap functions converts block
numbers to cluster numbers, and there's a special hack for mke2fs so
we don't burn a separate cluster for each allocation bitmap block.)
- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2014-04-30 2:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-28 14:09 [PATCH 1/2] libext2fs: fix alloc_allocate_group_table() if the flexbg_offset wraps Theodore Ts'o
2014-04-28 14:09 ` [PATCH 2/2] resize2fs: fix inode table move for the backwards move case Theodore Ts'o
2014-04-29 11:02 ` [PATCH 1/2] libext2fs: fix alloc_allocate_group_table() if the flexbg_offset wraps Lukáš Czerner
2014-04-30 2:34 ` 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=20140430023414.GC6714@thunk.org \
--to=tytso@mit.edu \
--cc=lczerner@redhat.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).