public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Valerie Clement <valerie.clement@bull.net>
To: Andreas Dilger <adilger@clusterfs.com>
Cc: Theodore Tso <tytso@mit.edu>,
	ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: [RFC][PATCH 1/12] new ext4 group desc struct in e2fsprogs
Date: Tue, 12 Jun 2007 13:44:22 +0200	[thread overview]
Message-ID: <466E8716.7080101@bull.net> (raw)
In-Reply-To: <20070611232120.GF5181@schatzie.adilger.int>

Andreas Dilger wrote:
> On Jun 11, 2007  18:42 +0200, Valerie Clement wrote:
>> @@ -213,7 +213,11 @@ struct struct_ext2_filsys {
>>  	int				fragsize;
>>  	dgrp_t				group_desc_count;
>>  	unsigned long			desc_blocks;
>> +#ifdef _EXT4FS_
>> +	struct ext4_group_desc *	group_desc;
>> +#else
>>  	struct ext2_group_desc *	group_desc;
>> +#endif
> 
> The way similar changes were incorporated into e2fsprogs in the past
> (e.g. large inode support) is to pass an ext2_group_desc around and
> in places where access to the "large" part of the struct are needed
> this is typecast and conditional upon the appropriate superblock field
> or feature, as it is in the kernel.  This also avoids the need to change
> the parameter everywhere.
> 
> This is important because even "ext4" filesystems may only have 32-byte
> group descriptors if they are formatted as ext3 and upgraded.
> 
> For large inodes, this is using "s_inode_size", and for the group
> descriptor it should use "s_desc_size" and INCOMPAT_64BIT.
> 

Yes, I see the problem. I'll make the changes in this way.
Thanks,
   Valérie

      reply	other threads:[~2007-06-12 11:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-11 16:42 [RFC][PATCH 1/12] new ext4 group desc struct in e2fsprogs Valerie Clement
2007-06-11 23:21 ` Andreas Dilger
2007-06-12 11:44   ` Valerie Clement [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=466E8716.7080101@bull.net \
    --to=valerie.clement@bull.net \
    --cc=adilger@clusterfs.com \
    --cc=linux-ext4@vger.kernel.org \
    --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