linux-kernel - Re: [RFC] tracefs

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: <20091025040503.GA15781@infradead.org>
Date:	Sun, 25 Oct 2009 00:05:03 -0400
From:	Christoph Hellwig <hch@...radead.org>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	Ingo Molnar <mingo@...e.hu>, Greg KH <greg@...ah.com>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Ingo Molnar <mingo@...hat.com>, linux-kernel@...r.kernel.org,
	Thomas Gleixner <tglx@...utronix.de>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>
Subject: Re: [RFC] tracefs

On Fri, Oct 23, 2009 at 09:12:08AM -0400, Steven Rostedt wrote:
> Note, I wasn't talking about tie down the pretty-print formats. But we
> need to have a standard way to change them.

Which means to tie down it I think.  Once we do have a good enough
format those bits need to be locked down, with a way for adding new
attributes (either entirely new or better replacmeents for existing
ones with leaving the old ones in place for existing userspace).

In addition to the format description people have also asked for ABI
tracepoints which would lock down the actual trace format in the
the same way (only addition of new fields without removing or changing
existing ones).  For this to be actually useful some trace buffer
also needs to be exposed in an ABI-stable (that is non-debugfs way).

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