linux-kernel - Re: [RFC PATCH 1/3] Unified trace 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:	Wed, 24 Sep 2008 16:48:43 -0400 (EDT)
From:	Steven Rostedt <rostedt@...dmis.org>
To:	David Miller <davem@...emloft.net>
cc:	torvalds@...ux-foundation.org, mbligh@...gle.com,
	peterz@...radead.org, linux-kernel@...r.kernel.org, mingo@...e.hu,
	tglx@...utronix.de, akpm@...ux-foundation.org,
	prasad@...ux.vnet.ibm.com, compudj@...stal.dyndns.org,
	fche@...hat.com, dwilder@...ibm.com, hch@....de,
	zanussi@...cast.net, srostedt@...hat.com
Subject: Re: [RFC PATCH 1/3] Unified trace buffer


On Wed, 24 Sep 2008, David Miller wrote:

> From: Linus Torvalds <torvalds@...ux-foundation.org>
> Date: Wed, 24 Sep 2008 13:23:47 -0700 (PDT)
> 
> > So I'd like the thing to have small headers, and be designed from the 
> > start to have small headers.
> 
> Small headers are good, but I'd suggest making sure there is an
> "offset" or similar field in there.
> 
> Not that I want to encourage frequent changes to header layout, but if
> you do need to add something, then this offset field allows you to do
> so while keeping existing analysis tools working.  They will just
> ignore the new information in the headers, but they will still be able
> to get at the data bits using the offset.

Right now I have a "length" field when fixed_length is not specified. This 
length is currently offest by 8 leaving all 8 bytes aligned.

We could change this to be variable? Would that help you?

-- Steve

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