From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Valerie Clement <valerie.clement@bull.net>,
linux-ext4 <linux-ext4@vger.kernel.org>
Cc: Mingming Cao <cmm@us.ibm.com>
Subject: Re: new mballoc patches.
Date: Wed, 12 Sep 2007 23:29:43 +0530 [thread overview]
Message-ID: <46E8290F.7020307@linux.vnet.ibm.com> (raw)
In-Reply-To: <46E7DF34.8090209@bull.net>
Valerie,
Valerie Clement wrote:
> Aneesh Kumar K.V wrote:
>>
>> running fsstress on ppc64 give me
>> EXT4-fs: group 9: 16384 blocks in bitmap, 32254 in gd
>> EXT4-fs error (device sda7): ext4_mb_mark_diskspace_used: Allocating
>> block in system zone - block = 294915
>>
>> EXT4-fs error (device sda7): ext4_ext_find_extent: bad header in inode
>> #213792: invalid magic - magic 5e5e, entries 24158, max 24158(0),
>> depth 24158(0)
>> RTAS: event: 137875, Type: Platform Error, Severity: 2
>> EXT4-fs error (device sda7): ext4_ext_find_extent: bad header in inode
>> #232149: invalid magic - magic e5e5, entries 58853, max 58853(0),
>> depth 58853(0)
>> RTAS: event: 137876, Type: Platform Error, Severity: 2
>> EXT4-fs error (device sda7): ext4_ext_find_extent: bad header in inode
>> #214332: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)
>> EXT4-fs error (device sda7): ext4_ext_remove_space: bad header in
>> inode #232149: invalid magic - magic e5e5, entries 58853, max
>> 58853(0), depth 58853(0)
>>
>> -aneesh
>
> endian problem?
> When running sparse on fs/ext4/ (make C=2 CF="-D__CHECK_ENDIAN__") :
>
> fs/ext4/extents.c:2570:12: warning: incorrect type in assignment
> (different base types)
> fs/ext4/extents.c:2570:12: expected unsigned long [unsigned]
> [assigned] allocated
> fs/ext4/extents.c:2570:12: got restricted unsigned short
> [addressable] [assigned] [usertype] ee_len
>
> I think the following line in extents.c
> allocated = newex.ee_len;
> should be replaced by
> allocated = le16_to_cpu(newex.ee_len);
>
>
Yes i guess that is the issue. fsstress is now running for the last 30 minutes without any error.
I have updated the patch series at
http://www.radian.org/~kvaneesh/ext4/patch-series/
Changes:
a) mballoc patch fixes for sparse warning
b) ext4_i_version_hi_2.patch patch fixes for sparse warning
c) Added commit message for ext4_uninit_blockgroup.patch
d) Added new patch sparse-fix.patch ( this can be pushed to upstream separately)
The complete patch set in
http://www.radian.org/~kvaneesh/ext4/patch-series/ext4-patch-queue.tar
-aneesh
next prev parent reply other threads:[~2007-09-12 18:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-11 8:29 new mballoc patches Aneesh Kumar K.V
2007-09-11 15:04 ` Aneesh Kumar K.V
[not found] ` <46E7DF34.8090209@bull.net>
2007-09-12 17:59 ` Aneesh Kumar K.V [this message]
2007-09-13 0:30 ` Mingming Cao
2007-09-11 23:18 ` Mingming Cao
2007-09-13 2:51 ` Aneesh Kumar K.V
2007-09-14 12:10 ` Aneesh Kumar K.V
2007-09-30 3:51 ` Alex Tomas
2007-09-27 5:58 ` Andrew Morton
2007-09-27 6:33 ` Aneesh Kumar K.V
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=46E8290F.7020307@linux.vnet.ibm.com \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=cmm@us.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=valerie.clement@bull.net \
/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).