linux-kernel - Re: changing format/size of data in TRACE_EVENT(extlog_mem

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] [day] [month] [year] [list]

Message-ID: <20150624205953.57ad77f1@gandalf.local.home>
Date:	Wed, 24 Jun 2015 20:59:53 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	"Luck, Tony" <tony.luck@...el.com>
Cc:	bp@...e.de, linux-edac@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: changing format/size of data in TRACE_EVENT(extlog_mem_event)

On Wed, 24 Jun 2015 14:56:49 -0700
"Luck, Tony" <tony.luck@...el.com> wrote:


> So the question is - how can we update the trace event to include these
> new wider fields with the minimum pain to applications that look at it?
> I don't know if there are any other consumers besides rasdaemon at the
> moment ... but we don't want ugly transitions where you have to guess
> which version of the application you need to run to work with a given
> kernel version.

It comes down to if the rasdaemon (and any other user) included the
event_parse.c "library" (it's not a public library yet, and we really
should make it one). Because if it did, it doesn't matter what the
field is, the event descriptions will give the size, and as long as the
name of a field exists, and it doesn't change type (that is, from
integer to string), it should be fine.

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