linux-kernel - Re: [PATCH 00/14] 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 for Android: free password hash cracker in your pocket

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

Message-ID: <4A401335.1090307@nortel.com>
Date:	Mon, 22 Jun 2009 17:26:45 -0600
From:	"Chris Friesen" <cfriesen@...tel.com>
To:	Pavel Machek <pavel@....cz>
CC:	Tim Bird <tim.bird@...sony.com>, Marco <marco.stornelli@...il.com>,
	Jamie Lokier <jamie@...reable.org>,
	Linux Embedded <linux-embedded@...r.kernel.org>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	Linux FS Devel <linux-fsdevel@...r.kernel.org>,
	Daniel Walker <dwalker@....ucsc.edu>
Subject: Re: [PATCH 00/14] Pramfs: Persistent and protected ram filesystem

Pavel Machek wrote:

> More politely said: "I believe you would be better off modifying
> ramdisk to include the functionality for persistence."  New filesystem
> should not really be neccessary. ext2 for performance, ext3 if you
> need robustness from journalling, maybe something else makes sense,
> too.

I agree that a persistent block device makes more sense.

However, as someone with some experience in using this type of
mechanism, a special filesystem (separate from the special block device)
could also be useful.  We often use things like circular buffers,
per-cpu areas, both log-structured and variable-length records, etc.  A
filesystem that would take care of this type of thing under the hood
might simplify a few things.

Also note that it's very useful for the kernel itself to be able to
access the contents of this persistent area...we use it for parts of the
log stream, various forms of "flight recorder" information, panic
tracebacks, etc. as well as making it available to select userspace apps.

Chris
--
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/