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]

Message-ID: <CA+55aFyG2jQFURwWebMWw7bAt3=zbXRsHSOtZVYBw-frUXqiRg@mail.gmail.com>
Date:	Fri, 11 May 2012 08:47:19 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Kay Sievers <kay@...y.org>
Cc:	Greg KH <gregkh@...uxfoundation.org>,
	Sasha Levin <levinsasha928@...il.com>,
	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 Fri, May 11, 2012 at 8:40 AM, Kay Sievers <kay@...y.org> wrote:
>
> Should we just pad the multi-newline-in-one-record output with 15
> spaces when printk_time is on?

Yeah, I think that would be the nicest thing.

Btw, I'd also *love* to see some model (eventually - not necessarily
now) where we could have the option of the time printouts being a bit
different (rather than just on/off). It would be very nice if we had
"relative" time printouts for events close together, so the rule could
be something like:

 - if time is same as last line, pad with empty

 - if time is more than a minute from last one, show an absolute value
of dd hh:mm:ss

 - otherwise, show a relative value of +ss.mmmmmm

So the on/off choice could be on/off/relative.

Hmm?

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