From: Wei Yongjun <yjwei@cn.fujitsu.com>
To: linux-ext4@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Theodore Tso <tytso@mit.edu>
Subject: ext3: Fix support for empty directory blocks in 64k blocksize filesystems
Date: Tue, 10 Feb 2009 16:36:27 +0800 [thread overview]
Message-ID: <49913C8B.2060605@cn.fujitsu.com> (raw)
The rec_len field in the directory entry is 16 bits, so if the
filesystem is completely empty, rec_len of 0 is used to designate
65536 in e2fsprogs, for the case where the directory entry takes
the entire 64k block.
But if empty directory is read, error message will be output by
current kernel. You can do the following commands to reproduct it.
- mkfs.ext3 -b $(( 64 * 1024 )) /dev/sdc1
- mount /dev/sda1 /mnt
- cd /mnt/lost+found
- ll
- tail /var/log/messages
EXT3-fs error (device sdc1): ext3_readdir: bad entry in \
directory #11: rec_len is smaller than minimal - offset=0, \
inode=0, rec_len=0, name_len=0
This patch fix to treat rec_len of 0 as 65536, like what e2fsprogs do.
Signed-off-by: Wei Yongjun <yjwei@cn.fujitsu.com>
---
include/linux/ext3_fs.h | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/include/linux/ext3_fs.h b/include/linux/ext3_fs.h
index dd495b8..dc975ad 100644
--- a/include/linux/ext3_fs.h
+++ b/include/linux/ext3_fs.h
@@ -711,7 +711,7 @@ static inline unsigned ext3_rec_len_from_disk(__le16 dlen)
{
unsigned len = le16_to_cpu(dlen);
- if (len == EXT3_MAX_REC_LEN)
+ if (len == EXT3_MAX_REC_LEN || len == 0)
return 1 << 16;
return len;
}
@@ -719,7 +719,7 @@ static inline unsigned ext3_rec_len_from_disk(__le16 dlen)
static inline __le16 ext3_rec_len_to_disk(unsigned len)
{
if (len == (1 << 16))
- return cpu_to_le16(EXT3_MAX_REC_LEN);
+ return cpu_to_le16(0);
else if (len > (1 << 16))
BUG();
return cpu_to_le16(len);
--
1.5.3.8
reply other threads:[~2009-02-10 8:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=49913C8B.2060605@cn.fujitsu.com \
--to=yjwei@cn.fujitsu.com \
--cc=akpm@linux-foundation.org \
--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 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.