linux-kernel - Re: [PATCH] perf: make perf.data more self-descriptive (v4)

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: <CABPqkBR66vzNz7+MxtFk_zmpBTFqAX83he7kGB2+HALK9xbkWQ@mail.gmail.com>
Date:	Fri, 16 Sep 2011 18:34:50 +0200
From:	Stephane Eranian <eranian@...gle.com>
To:	David Ahern <dsahern@...il.com>
Cc:	Peter Zijlstra <peterz@...radead.org>,
	linux-kernel@...r.kernel.org, acme@...hat.com, mingo@...e.hu
Subject: Re: [PATCH] perf: make perf.data more self-descriptive (v4)

On Fri, Sep 16, 2011 at 5:33 PM, David Ahern <dsahern@...il.com> wrote:
>
>
> On 09/16/2011 09:19 AM, Peter Zijlstra wrote:
>> On Fri, 2011-09-16 at 08:50 -0600, David Ahern wrote:
>>>
>>> ppc data file: header->magic 454c494646524550
>>> x86 data file: header->magic 454c494646524550
>>>
>> Ok then we need to fix that magic thing..
>
> Right, but it breaks backwards/forwards compatibility. e.g.,
>
Not necessarily, if you keep the current MAGIC, then you detect
a file with the old format, i.e., no flexibility on attr_size.

Then, you pick two new MAGIC numbers. They must, of course,
reflect the endianness. Those new perf.data files won't work with
older perf for sure, but at least you can maintain backward
compatibility. The new MAGIC must, of course, reflect the
endianness.



> diff --git a/tools/perf/util/header.c b/tools/perf/util/header.c
> index 73fa59e..603a8bb9 100644
> --- a/tools/perf/util/header.c
> +++ b/tools/perf/util/header.c
> @@ -65,9 +65,7 @@ char *perf_header__find_event(u64 id)
>    return NULL;
>  }
>
> -static const char *__perf_magic = "PERFFILE";
> -
> -#define PERF_MAGIC (*(u64 *)__perf_magic)
> +#define PERF_MAGIC 0x5045524646494c45ULL  // "PERFFILE"
>
>  struct perf_file_attr {
>    struct perf_event_attr  attr;
>
> That puts the magic in the file based on endianness of the recording
> system. e.g., on x86:
>
> $ od -c perf-magic.data | head -1
> 0000000   E   L   I   F   F   R   E   P   h  \0  \0  \0  \0  \0  \0  \0
>
> Which means older perf binaries can't analyze new files (created with
> new magic order) and newer perf binaries can't analyze older perf files
> -- the new command will incorrectly want to do endian swapping on the
> old file.
>
> David
>
--
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/