| 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
| ||
|
Message-ID: <483.1445519966@warthog.procyon.org.uk> Date: Thu, 22 Oct 2015 14:19:26 +0100 From: David Howells <dhowells@...hat.com> To: Petr Mladek <pmladek@...e.com> Cc: dhowells@...hat.com, linux-kernel@...r.kernel.org, jack@...e.cz, will.deacon@....com, rostedt@...dmis.org, dwmw2@...radead.org, Andrew Morton <akpm@...ux-foundation.org> Subject: Re: [PATCH] printk: Don't discard earlier unprinted messages to make space Petr Mladek <pmladek@...e.com> wrote: > I would expect that the first few messages are printed to the console > before the buffer is wrapped. IMHO, in many cases, you are interested > into the final messages that describe why the system went down. The last message might tell you that the machine panicked because the NMI handler triggered due to a spinlocked section taking too long or something. This doesn't help if the oops that caused the spinlock to remain held or whatever gets discarded from the buffer due to several intervening complaints that result secondarily from the initial oops. > If there is no time to print them, you want to have them in the crash dump > (ring buffer) at least. But not at the expense of discarding the first oops report. *That* one is the most important. Perhaps things could be arranged such that messages *can* be discarded from the front of the buffer *provided* they are not oops messages. 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/
Powered by blists - more mailing lists