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: <32058.1292926258@redhat.com>
Date:	Tue, 21 Dec 2010 10:10:58 +0000
From:	David Howells <dhowells@...hat.com>
To:	Huang Ying <ying.huang@...el.com>
Cc:	dhowells@...hat.com, "Luck, Tony" <tony.luck@...el.com>,
	Borislav Petkov <bp@...en8.de>,
	Tony Luck <tony.luck@...il.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	"H. Peter Anvin" <hpa@...or.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-arch@...r.kernel.org" <linux-arch@...r.kernel.org>,
	"tglx@...utronix.de" <tglx@...utronix.de>,
	"mingo@...e.hu" <mingo@...e.hu>, "greg@...ah.com" <greg@...ah.com>,
	"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
	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

Huang Ying <ying.huang@...el.com> wrote:

> > > - for OOPS messages will not cause system panic, it will go to disk and
> > > will not use up the persistent storage.
> > 
> > You can't guarantee that an oops didn't just kill your ability to actually
> > write your syslog to disk or out across the network.
> 
> I do not need to guarantee that. If the OOPS message can not be written
> to disk, just keeping it in persistent storage, and that is the very
> value of persistent storage.  But for OOPS can go to disk safely, we do
> not need to waste persistent storage for it.

My point is how do you know an oops message will actually manage to get to
disk?  There's a userspace program (syslogd) between the kernel log and the
disk or network.

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