From: Thiemo Nagel <thiemo.nagel@ph.tum.de>
To: Theodore Tso <tytso@mit.edu>,
Alexander Beregalov <a.beregalov@gmail.com>,
Jens Axboe <jens.axboe@oracle.com>,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: 2.6.29-git: cannot mount ext4/loop
Date: Thu, 02 Apr 2009 17:18:39 +0200 [thread overview]
Message-ID: <49D4D74F.1020904@ph.tum.de> (raw)
In-Reply-To: <20090402145436.GF10642@mit.edu>
Theodore Tso wrote:
> On Thu, Apr 02, 2009 at 03:30:26PM +0200, Thiemo Nagel wrote:
>> When I added the block range checks, initially I was assuming that
>> when EXTENTS_FL is not set, the inode->i_data *always* contains
>> references to further blocks. Ted showed me wrong and added the condition
>>
>> ISREG() || ISDIR() || ( ISLNK() && !is_fast_symlink() )
>>
>> before that assumption can be made. But maybe we need some further
>> restraints?
>
> It's a endian-problem; we're missing le32_to_cpu() in that patch.
> Sparc is big-endian.
Sorry for that.
Thiemo
---
diff --git a/fs/ext4/inode.c b/fs/ext4/inode.c
index 98e289a..ec3555d 100644
--- a/fs/ext4/inode.c
+++ b/fs/ext4/inode.c
@@ -377,11 +377,11 @@ static int __ext4_check_blockref(const char
*function, struct inode *inode,
unsigned int maxblocks =
ext4_blocks_count(EXT4_SB(inode->i_sb)->s_es);
unsigned int *bref = p;
while (bref < p+max) {
- if (unlikely(*bref >= maxblocks)) {
+ if (unlikely(le32_to_cpu(*bref) >= maxblocks)) {
ext4_error(inode->i_sb, function,
"block reference %u >= max (%u) "
"in inode #%lu, offset=%d",
- *bref, maxblocks,
+ le32_to_cpu(*bref), maxblocks,
inode->i_ino, (int)(bref-p));
return -EIO;
}
next prev parent reply other threads:[~2009-04-02 15:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-01 21:23 2.6.29-git: cannot mount ext4/loop Alexander Beregalov
2009-04-01 22:53 ` Alexander Beregalov
2009-04-01 22:53 ` Alexander Beregalov
2009-04-02 5:53 ` Theodore Tso
2009-04-02 7:42 ` Alexander Beregalov
2009-04-02 7:42 ` Alexander Beregalov
2009-04-02 11:39 ` Alexander Beregalov
2009-04-02 11:39 ` Alexander Beregalov
2009-04-02 12:47 ` Alexander Beregalov
2009-04-02 12:47 ` Alexander Beregalov
2009-04-02 13:30 ` Thiemo Nagel
2009-04-02 14:54 ` Theodore Tso
2009-04-02 15:18 ` Thiemo Nagel [this message]
2009-04-02 15:41 ` Theodore Tso
2009-04-02 17:05 ` Thiemo Nagel
2009-04-02 18:29 ` Alexander Beregalov
2009-04-02 18:29 ` Alexander Beregalov
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=49D4D74F.1020904@ph.tum.de \
--to=thiemo.nagel@ph.tum.de \
--cc=a.beregalov@gmail.com \
--cc=jens.axboe@oracle.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.