linux-kernel - Re: [concept & "good taste" review] persistent store

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20101219180109.3c042e43@schatten.dmk.lab>
Date:	Sun, 19 Dec 2010 18:01:09 +0100
From:	Florian Mickler <florian@...kler.org>
To:	Borislav Petkov <bp@...en8.de>
Cc:	Tony Luck <tony.luck@...il.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	"H. Peter Anvin" <hpa@...or.com>, linux-kernel@...r.kernel.org,
	linux-arch@...r.kernel.org, tglx@...utronix.de, mingo@...e.hu,
	greg@...ah.com, akpm@...ux-foundation.org, ying.huang@...el.com,
	David Miller <davem@...emloft.net>,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Jim Keniston <jkenisto@...ux.vnet.ibm.com>,
	Kyungmin Park <kmpark@...radead.org>,
	Geert Uytterhoeven <geert@...ux-m68k.org>
Subject: Re: [concept & "good taste" review] persistent store

On Sun, 19 Dec 2010 10:17:52 +0100
Borislav Petkov <bp@...en8.de> wrote:

> On Sat, Dec 18, 2010 at 03:06:57PM -0800, Tony Luck wrote:
> > > Doesn't that sound like the best of both worlds?
> > 
> > It sounds like an excellent heuristic for how the platform layer
> > should manage the persistent store when space is tight. But
> > I think that I can still keep my /dev/pstore filesystem as a
> > presentation layer to make the bits available to the user in
> > a device independent way.
I agree. As far as I understand, Linus concept could map nicely onto an
fs:

1. marking things read:
	Clients can delete files as soon as they have savely scribled
	them down somewhere. 

2. on boot the persistent storage layer init's any files in an
'archive' directory. 

3. if an oops happens, the persistent storage layer shows them in the
pstore-root directory. If no space is left, the
persistent storage layer evicts as much oldest entries from the
'archive' as necessary. as soon as archive is empty but the pstore is
full, pstore stops storing new oopses.

Or not? That way, there would be some sort of journal behaviour, but
also new oopses will evict old(pre-boot) oopses if necessary. 
maybe a kernel boot-parameter to disable deleting old oopses could be
necessary in some cases. But I doubt it.

Regards, 
Flo

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