From: Coly Li <coyli@suse.de>
To: linux-ext4@vger.kernel.org
Subject: [PATCH][e2fsprogs] extend bg_itable_unused into 32bit
Date: Mon, 15 Oct 2007 15:34:35 +0800 [thread overview]
Message-ID: <4713180B.5080000@suse.de> (raw)
Current bg_itable_unused in ext2_group_desc and ext4_group_desc is 16bit, which can present 64K
inode offset in inodes table at most. For 4KB ext4 block, the inode bitmap can present 32K inodes in
inodes table at most.
It is very easy to encounter this size limitation in future ext4 development -- we need to extend
this field into 32bit for ext4.
In latest e2fsprogs git, it seems only adding a bg_itable_unused_hi in struct ext4_group_desc is OK
(do not interfere current e2fsprogs and kernel code).
Signed-off-by: Coly Li <coyli@suse.de>
---
diff --git a/lib/ext2fs/ext2_fs.h b/lib/ext2fs/ext2_fs.h
index a316665..2aeb6d4 100644
--- a/lib/ext2fs/ext2_fs.h
+++ b/lib/ext2fs/ext2_fs.h
@@ -167,7 +167,7 @@ struct ext4_group_desc
__u16 bg_free_blocks_count_hi;/* Free blocks count MSB */
__u16 bg_free_inodes_count_hi;/* Free inodes count MSB */
__u16 bg_used_dirs_count_hi; /* Directories count MSB */
- __u16 bg_pad;
+ __u16 bg_itable_unused_hi; /* Unused inodes count MSB */
__u32 bg_reserved2[3];
};
--
Coly Li
SuSE PRC Labs
reply other threads:[~2007-10-15 7:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4713180B.5080000@suse.de \
--to=coyli@suse.de \
--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).