[PATCH 00/16 v4] pramfs: persistent and protected RAM filesystem

[PATCH 00/16 v4] pramfs: persistent and protected RAM filesystem

[Marco Stornelli]

Hi all,

fourth round for the patch series. I summarize here the changes to
improve the review:

v4:
- in bitmap init used already present bitmap_set function
- fix a possible memory leak in an error path reported by yidong zhang

v3:
- fix a possible memory leak in an error path reported by yidong zhang
- fix a warning when using XIP about not used __pram_mmap symbol
- fix test module header description and replaced TEST_MODULE with
PRAMFS_TEST_MODULE in the Kconfig and Makefile according to the comments
done by Randy Dunlap
- fix a compilation warning in super.c reported by James Hogan
- fix a compilation error when XIP was enabled
- removed not used symbol PRAM_XATTR_INDEX_LUSTRE
- fix some comment style issue

v2:
- fix documentation errors reported by Randy Dunlap and Kieran Bingham
- reworked memory write protection functions with the suggestions of
Andi Kleen

v1:
- first draft

Andrew/Greg, can you insert the code in the mm/staging tree?

Marco

Re: [PATCH 00/16 v4] pramfs: persistent and protected RAM filesystem

[Marco]

Il 20/11/2010 10:56, Marco Stornelli ha scritto:
> 
> Andrew/Greg, can you insert the code in the mm/staging tree?
> 

Please, can I have a positive/negative feedback about that? Thanks.

Marco

Re: [PATCH 00/16 v4] pramfs: persistent and protected RAM filesystem

[Greg KH]

On Mon, Nov 22, 2010 at 07:11:48PM +0100, Marco wrote:
> Il 20/11/2010 10:56, Marco Stornelli ha scritto:
> > 
> > Andrew/Greg, can you insert the code in the mm/staging tree?
> > 
> 
> Please, can I have a positive/negative feedback about that? Thanks.

I can add it to the staging tree _if_ the code is under drivers/staging/
which I do not think your patch places the code at, right?

So if you wish to do that, I'd be glad to take it, but you need to have
a list of things left to do to get it integrated into the "main" portion
of the kernel.  Do you have that at the moment?

thanks,

greg k-h