[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20081229124759.d21e1410.akpm@linux-foundation.org>
Date: Mon, 29 Dec 2008 12:47:59 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Boaz Harrosh <bharrosh@...asas.com>
Cc: avishay@...il.com, jeff@...zik.org, viro@...IV.linux.org.uk,
linux-fsdevel@...r.kernel.org, osd-dev@...n-osd.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 5/9] exofs: dir_inode and directory operations
On Tue, 16 Dec 2008 17:28:57 +0200
Boaz Harrosh <bharrosh@...asas.com> wrote:
> implementation of directory and inode operations.
>
> * A directory is treated as a file, and essentially contains a list
> of <file name, inode #> pairs for files that are found in that
> directory. The object IDs correspond to the files' inode numbers
> and are allocated using a 64bit incrementing global counter.
> * Each file's control block (AKA on-disk inode) is stored in its
> object's attributes. This applies to both regular files and other
> types (directories, device files, symlinks, etc.).
>
> ...
>
> fs/exofs/dir.c | 649 ++++++++++++++++++++++++++++++++++++++++++++++++++++++
yes, this does look rather ext2-like ;)
How long ago was the code cloned from ext2? iirc there have been a
number of fairly subtle bugs fixed in ext2/dir.c over the past year or
three. If the code was not quite recently cloned then I'd suggest that
you spend a bit of time looking through the ext2 changelogs, see if
there are any bugfixes which needs to be ported.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists