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:	Sat, 12 May 2012 14:04:24 -0400
From:	Mark Lord <kernel@...savvy.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
CC:	Kay Sievers <kay@...y.org>, 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 12-05-11 04:02 PM, Linus Torvalds wrote:
> On Fri, May 11, 2012 at 12:51 PM, Mark Lord <kernel@...savvy.com> wrote:
>>
>> Breaks the "grep for specific messages" case.
> 
> Why?
> 
> Sure, if you grep for times, you'd not want to enable the relative
> time. But why would you grep for a time anyway? Regardless, it would
> be your choice.


I'd be grepping for specific message content, not times.
But I'd want to see the times for the messages,
to know if they're related events or not.

Relative times are great, no problem there.
But relative to what?  The previous message?

That's no good unless viewing all messages,
rather than a grep'd subset.

But with a choice, we do get the best of both, so no problemo.

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