public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Peter Staubach <staubach@redhat.com>
Cc: linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH]: ext4: fix big endian
Date: Thu, 6 Nov 2008 17:15:53 +0100	[thread overview]
Message-ID: <200811061715.53593.borntraeger@de.ibm.com> (raw)
In-Reply-To: <49131601.50407@redhat.com>

Am Donnerstag, 6. November 2008 schrieb Peter Staubach:
> >  	/* We allocate both existing and potentially added groups */
> >  	flex_group_count = ((sbi->s_groups_count + groups_per_flex - 1) +
> > -			    ((sbi->s_es->s_reserved_gdt_blocks +1 ) <<
> > +			    (le16_to_cpu(sbi->s_es->s_reserved_gdt_blocks + 1) <<
> >   
> 
> I suspect that you want to do the le16_to_cpu() and _then_
> add the 1.  Otherwise, adding 1 to a different byte order
> value won't do quite what is expected or hoped for...

errm. Right.
Something like this maybe?

[PATCH]: ext4: fix big endian access for flex groups

On big endianess plattforms newly created ext4 file systems cannot be mounted
and show messages like:
[6923911.715968] EXT4-fs: not enough memory for 522250 flex groups
[6923911.715973] EXT4-fs: unable to initialize flex_bg meta info!

We have to access s_reserved_gdb_blocks with le16_to_cpu.

Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
---
 fs/ext4/super.c |    4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

Index: kvm/fs/ext4/super.c
===================================================================
--- kvm.orig/fs/ext4/super.c
+++ kvm/fs/ext4/super.c
@@ -1455,8 +1455,8 @@ static int ext4_fill_flex_info(struct su
 
 	/* We allocate both existing and potentially added groups */
 	flex_group_count = ((sbi->s_groups_count + groups_per_flex - 1) +
-			    ((sbi->s_es->s_reserved_gdt_blocks +1 ) <<
-			      EXT4_DESC_PER_BLOCK_BITS(sb))) /
+			    ((le16_to_cpu(sbi->s_es->s_reserved_gdt_blocks) +
+			      1) << EXT4_DESC_PER_BLOCK_BITS(sb))) /
 			   groups_per_flex;
 	sbi->s_flex_groups = kzalloc(flex_group_count *
 				     sizeof(struct flex_groups), GFP_KERNEL);

  reply	other threads:[~2008-11-06 16:17 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-06 15:00 EXT4-fs: not enough memory for 522250 flex groups Christian Borntraeger
2008-11-06 15:51 ` [PATCH]: ext4: fix big endian (was: not enough memory for 522250 flex groups) Christian Borntraeger
2008-11-06 16:06   ` [PATCH]: ext4: fix big endian Peter Staubach
2008-11-06 16:15     ` Christian Borntraeger [this message]
2008-11-06 16:32       ` Aneesh Kumar K.V
2008-11-06 16:38     ` Christoph Hellwig
2008-11-06 17:11       ` Christian Borntraeger
2008-11-06 17:33       ` Theodore Tso
2008-11-06 17:39         ` Christoph Hellwig
2008-11-06 17:48           ` Alexey Dobriyan
2008-11-08 22:35           ` Jörn Engel
2008-11-10 18:09             ` Harvey Harrison
2008-11-10 19:31               ` Jörn Engel
2008-11-06 16:06   ` [PATCH]: ext4: fix big endian (was: not enough memory for 522250 flex groups) Andreas Schwab
2008-11-06 16:59   ` Theodore Tso

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=200811061715.53593.borntraeger@de.ibm.com \
    --to=borntraeger@de.ibm.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=staubach@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