public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Dilger <andreas.dilger@oracle.com>
To: Valerie Aurora <vaurora@redhat.com>
Cc: Eric Sandeen <sandeen@redhat.com>,
	"linux-ext4@vger.kernel.orgdevelopment"
	<linux-ext4@vger.kernel.org>
Subject: Re: problems with large group descriptors and 64bit
Date: Thu, 24 Jun 2010 18:35:16 -0600	[thread overview]
Message-ID: <BE781EC4-8A82-478F-8D10-BC19C0664567@oracle.com> (raw)
In-Reply-To: <20100624174117.GD22760@shell>


On 2010-06-24, at 11:41 AM, Valerie Aurora <vaurora@redhat.com> wrote:

> On Tue, Jun 22, 2010 at 05:24:34PM -0600, Andreas Dilger wrote:
> 
>> lib/ext2fs/blknum.c assumes 64BIT means ext4_group_desc, not s_desc_size:
>> struct ext2_group_desc *ext2fs_group_desc(ext2_filsys fs,
>>                                          struct opaque_ext2_group_desc *gdp,
>>                                          dgrp_t group)
>> {               
>>        if (fs->super->s_desc_size >= EXT2_MIN_DESC_SIZE_64BIT)
>>                return (struct ext2_group_desc *)
>>                        ((struct ext4_group_desc *) gdp + group);
>>        else
>>                return (struct ext2_group_desc *) gdp + group;
>> }
> 
> I'm not sure I understand.  Are there more than two possible sizes for
> group descriptors?  Or is the existing code correct but you'd like to
> use s_desc_size directly for simplicity?

When the 64BIT flag is set the size kid the group descriptor is given by s_group_desc, which is currently the same as struct ext4_group_desc, but it might be larger in the future. 

      reply	other threads:[~2010-06-25  0:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-22 23:24 problems with large group descriptors and 64bit Andreas Dilger
2010-06-24 17:41 ` Valerie Aurora
2010-06-25  0:35   ` Andreas Dilger [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=BE781EC4-8A82-478F-8D10-BC19C0664567@oracle.com \
    --to=andreas.dilger@oracle.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=sandeen@redhat.com \
    --cc=vaurora@redhat.com \
    /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