From: Marco Stornelli <marco.stornelli@gmail.com>
To: sfr@canb.auug.org.au, Andrew Morton <akpm@linux-foundation.org>,
dwmw2@infradead.org, mpm@selenic.com
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Linux FS Devel <linux-fsdevel@vger.kernel.org>,
Linux Embedded <linux-embedded@vger.kernel.org>,
Tim Bird <tim.bird@am.sony.com>
Subject: Re: [PATCH 00/17] pramfs: persistent and protected RAM filesystem
Date: Tue, 11 Jan 2011 20:01:38 +0100 [thread overview]
Message-ID: <4D2CA912.5070308@gmail.com> (raw)
In-Reply-To: <4D25AEEE.1050401@gmail.com>
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
prev parent reply other threads:[~2011-01-11 19:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-06 12:00 [PATCH 00/17] pramfs: persistent and protected RAM filesystem Marco Stornelli
2011-01-06 14:03 ` Peter Zijlstra
2011-01-06 16:26 ` Marco Stornelli
2011-01-06 16:58 ` Marco Stornelli
2011-01-06 18:22 ` Luck, Tony
2011-01-06 18:31 ` Marco Stornelli
2011-01-11 13:33 ` Pavel Machek
2011-01-11 19:01 ` Marco Stornelli [this message]
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=4D2CA912.5070308@gmail.com \
--to=marco.stornelli@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=dwmw2@infradead.org \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=sfr@canb.auug.org.au \
--cc=tim.bird@am.sony.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).