summaryrefslogtreecommitdiff
path: root/fs/jffs2
diff options
context:
space:
mode:
authorWei Yongjun <yjwei@cn.fujitsu.com>2009-02-10 17:53:42 +0300
committerTheodore Tso <tytso@mit.edu>2009-02-10 17:53:42 +0300
commit7be2baaa0322c59ba888aa5260a8c130666acd41 (patch)
treea1543a38923d60092e06741ab3dee9ce9af32abc /fs/jffs2
parent7f5aa215088b817add9c71914b83650bdd49f8a9 (diff)
downloadlinux-7be2baaa0322c59ba888aa5260a8c130666acd41.tar.xz
ext4: Fix to read empty directory blocks correctly in 64k
The rec_len field in the directory entry is 16 bits, so there was a problem representing rec_len for filesystems with a 64k block size in the case where the directory entry takes the entire 64k block. Unfortunately, there were two schemes that were proposed; one where all zeros meant 65536 and one where all ones (65535) meant 65536. E2fsprogs used 0, whereas the kernel used 65535. Oops. Fortunately this case happens extremely rarely, with the most common case being the lost+found directory, created by mke2fs. So we will be liberal in what we accept, and accept both encodings, but we will continue to encode 65536 as 65535. This will require a change in e2fsprogs, but with fortunately ext4 filesystems normally have the dir_index feature enabled, which precludes having a completely empty directory block. Signed-off-by: Wei Yongjun <yjwei@cn.fujitsu.com> Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
Diffstat (limited to 'fs/jffs2')
0 files changed, 0 insertions, 0 deletions