linux-kernel - Re: [PATCH] pramfs: Persistent and protected RAM filesystem

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Wed, 6 Oct 2010 09:24:56 +0900
From:	Minchan Kim <minchan.kim@...il.com>
To:	Marco Stornelli <marco.stornelli@...il.com>
Cc:	Linux Kernel <linux-kernel@...r.kernel.org>,
	linux-embedded@...r.kernel.org, linux-fsdevel@...r.kernel.org,
	Tim Bird <tim.bird@...sony.com>, linux-mm@...ck.org
Subject: Re: [PATCH] pramfs: Persistent and protected RAM filesystem

Hello.

On Tue, Oct 5, 2010 at 8:39 PM, Marco Stornelli
<marco.stornelli@...il.com> wrote:
> Hi all,
>
> after a lot of improvement, test, bug fix and new features, it's the
> moment for third round with the kernel community to submit PRAMFS for
> mainline. First of all, I have to say thanks to Tim Bird and CELF to
> actively support the project.

Good to know.
Thanks for your endless effort. :)

>
> Since the last review (June 2009) a lot of things are changed:
>
> - removed any reference of BKL
> - fixed the endianess for the fs layout
> - added support for extended attributes, ACLs and security labels
> - moved out any pte manipulations from fs and inserted them in mm
> - implemented the new truncate convention
> - fixed problems with 64bit archs
>
> ...and much more. Complete "story" in the ChangeLog inserted in the
> documentation file.
>
> Since the patch is long, you can download and review the patch from
> the project site: http:\\pramfs.sourceforge.net. The patch version is
> 1.2.1 for kernel 2.6.36.
> In addition, in the web site tech page, you can find a lot of
> information about implementation, technical details, benchemarking and
> so on.

If you really want to merge it, you have to divide patch into
individual patches instead of all-at-once patch.
Individual patches should have a description and clear feature to
review more easily.
And still we need all-at-once patch to apply the patch and test easily.

> Regards,
>
> Marco
>
> --
> To unsubscribe, send a message with 'unsubscribe linux-mm' in
> the body to majordomo@...ck.org.  For more info on Linux MM,
> see: http://www.linux-mm.org/ .
> Don't email: <a href=mailto:"dont@...ck.org"> email@...ck.org </a>
>
>



-- 
Kind regards,
Minchan Kim
--
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/