linux-kernel - Re: [PATCH RESEND 1/3] printk: convert byte-buffer to variable-length record buffer

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]

Date:	Mon, 14 May 2012 12:40:32 -0400
From:	valdis.kletnieks@...edu
To:	Mark Lord <kernel@...savvy.com>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Sasha Levin <levinsasha928@...il.com>,
	Kay Sievers <kay@...y.org>,
	Greg KH <gregkh@...uxfoundation.org>,
	Yinghai Lu <yinghai@...nel.org>, Joe Perches <joe@...ches.com>,
	Ingo Molnar <mingo@...nel.org>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH RESEND 1/3] printk: convert byte-buffer to variable-length record buffer

On Sun, 13 May 2012 09:22:04 -0400, Mark Lord said:
> On 12-05-12 02:35 PM, Linus Torvalds wrote:
> > I dunno. The above is what I would have liked to see quite often. I
> > look at dmesg, and notice that I had an WARN_ON_ONCE in it, and I have
> > no idea when it happened, because the "seconds since boot" is totally
> > useless information for me, as I'm too lazy to try to use /proc/uptime
> > to calculate what it is.

> Look in syslog ?

Oddly enough, just yesterday I was looking in dmesg on one of my servers, trying to
find a hint of why syslog and a number of other things had failed to start at boot...



Content of type "application/pgp-signature" skipped