> Since -pre3, ext2 (and perhaps other FSs, I haven't checked) uses an
> in-core inode layout consisting of an FS-specific head followed by the
> generic inode. ext2 allocates these in fs/ext2/super.c:ext2_alloc_inode(),
> but doesn't clear the ext2-specific fields. fs/inode.c:alloc_inode()
> neither knows about these fields nor clears them, so the ext2-specific
> data remains uninitialised when the new inode is returned for use. Ouch.
>
> The patch below fixes this by adding the missing memset() to
> fs/ext2/super.c:ext2_alloc_inode(). Works fine over here.
This is very odd, since ext2_new_inode() and ext2_read_inode() _do_
clean (or otherwise set) them. Let me check...
Arrgh. 1 missing in ext2_new_inode() and 1 (harmless) in ext2_read_inode()
--- C3-pre4/fs/ext2/ialloc.c Wed Jan 23 20:45:32 2002
+++ /tmp/ialloc.c Thu Jan 24 21:41:52 2002
@@ -392,6 +392,7 @@
ei->i_flags &= ~(EXT2_IMMUTABLE_FL|EXT2_APPEND_FL);
ei->i_faddr = 0;
ei->i_frag_no = 0;
+ ei->i_frag_size = 0;
ei->i_osync = 0;
ei->i_file_acl = 0;
ei->i_dir_acl = 0;
and
--- C3-pre4/fs/ext2/inode.c Wed Jan 23 20:45:32 2002
+++ /tmp/inode.c Thu Jan 24 21:44:48 2002
@@ -963,6 +963,7 @@
ei->i_frag_size = raw_inode->i_fsize;
ei->i_osync = 0;
ei->i_file_acl = le32_to_cpu(raw_inode->i_file_acl);
+ ei->i_dir_acl = 0;
if (S_ISREG(inode->i_mode))
inode->i_size |= ((__u64)le32_to_cpu(raw_inode->i_size_high)) << 32;
else
resp.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/