[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4D2CA912.5070308@gmail.com>
Date: Tue, 11 Jan 2011 20:01:38 +0100
From: Marco Stornelli <marco.stornelli@...il.com>
To: sfr@...b.auug.org.au, Andrew Morton <akpm@...ux-foundation.org>,
dwmw2@...radead.org, mpm@...enic.com
CC: Linux Kernel <linux-kernel@...r.kernel.org>,
Linux FS Devel <linux-fsdevel@...r.kernel.org>,
Linux Embedded <linux-embedded@...r.kernel.org>,
Tim Bird <tim.bird@...sony.com>
Subject: Re: [PATCH 00/17] pramfs: persistent and protected RAM filesystem
Hi all,
On 06/01/2011 13:00, Marco Stornelli wrote:
> Hi all,
>
> after several reviews is time to submit the code for mainline. Thanks to
> CELF to believe and support actively the project and thanks to Tim Bird.
>
> Here the stats:
>
> Documentation/filesystems/pramfs.txt | 179 ++++++
> Documentation/filesystems/xip.txt | 2 +
> arch/Kconfig | 3 +
> arch/x86/Kconfig | 1 +
> fs/Kconfig | 8 +-
> fs/Makefile | 1 +
> fs/pramfs/Kconfig | 72 +++
> fs/pramfs/Makefile | 14 +
> fs/pramfs/acl.c | 433 +++++++++++++
> fs/pramfs/acl.h | 86 +++
> fs/pramfs/balloc.c | 147 +++++
> fs/pramfs/desctree.c | 181 ++++++
> fs/pramfs/desctree.h | 44 ++
> fs/pramfs/dir.c | 208 +++++++
> fs/pramfs/file.c | 326 ++++++++++
> fs/pramfs/inode.c | 848 ++++++++++++++++++++++++++
> fs/pramfs/ioctl.c | 121 ++++
> fs/pramfs/namei.c | 371 ++++++++++++
> fs/pramfs/pram.h | 269 +++++++++
> fs/pramfs/pramfs_test.c | 47 ++
> fs/pramfs/super.c | 940 +++++++++++++++++++++++++++++
> fs/pramfs/symlink.c | 76 +++
> fs/pramfs/wprotect.c | 41 ++
> fs/pramfs/wprotect.h | 151 +++++
> fs/pramfs/xattr.c | 1104 ++++++++++++++++++++++++++++++++++
> fs/pramfs/xattr.h | 131 ++++
> fs/pramfs/xattr_security.c | 78 +++
> fs/pramfs/xattr_trusted.c | 65 ++
> fs/pramfs/xattr_user.c | 68 +++
> fs/pramfs/xip.c | 83 +++
> fs/pramfs/xip.h | 28 +
> include/linux/magic.h | 1 +
> include/linux/pram_fs.h | 130 ++++
> include/linux/pram_fs_sb.h | 45 ++
> 34 files changed, 6299 insertions(+), 3 deletions(-)
>
Can I have a feedback to insert this fs in the linux-next? From this
latest review I received some comments about how to fix some fs problems
on-the-fly without to clean all and restart. My next step will be to
write a simple fsck.pram to allow to fix these situations. However I
think the kernel code it's mature to be inserted in a pre-mainline
container. If I'll receive a positive feedback to my question, I'll
repost the patches to the last version (I updated the fs to be RCU aware
according to the work of Nick).
Marco
--
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