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
| ||
|
Date: Mon, 20 Dec 2010 13:09:41 -0800 From: Tony Luck <tony.luck@...el.com> To: Borislav Petkov <bp@...en8.de>, Linus Torvalds <torvalds@...ux-foundation.org>, Tony Luck <tony.luck@...el.com>, Tony Luck <tony.luck@...il.com>, "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 Mon, Dec 20, 2010 at 10:58 AM, Borislav Petkov <bp@...en8.de> wrote: > Yes, this was exactly what I was trying to say! Do something in a > watchdog handler path that shows that we actually made progress. But > you're right, we'd still need the notification. My look at "did we make > a progress" was too simple and there _are_ nuances which need to be > accounted for. My view of the notification is: 1) Oops happens, gets written to persistent store. 2) fs/pstore code makes a file appear in /dev/pstore 3) Daemon that's watching /dev/pstore sees new file 4) File is read, copied some place safe and fsync'd 5) Daemon unlinks file from /dev/pstore 6) fs/pstore code tells platform level to erase record -Tony -- 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/
Powered by blists - more mailing lists