From: Milian Wolff <milian.wolff@kdab.com>
To: linux-perf-users@vger.kernel.org
Cc: Chun-Tse Shao <ctshao@google.com>, acme@kernel.org
Subject: combined usage of `--aio -z` corrupts perf.data files - fallout from COMPRESSED2?
Date: Wed, 10 Sep 2025 10:51:31 +0200 [thread overview]
Message-ID: <38208379.DOZC079dcN@milian-workstation> (raw)
Hey all,
for some context, see https://github.com/KDAB/hotspot/issues/
736#issuecomment-3273734660
The gist is the following:
```
$ perf record --call-graph dwarf -z --aio -- ls
...
[ perf record: Captured and wrote 0.005 MB perf.data, compressed (original
0.101 MB, ratio is 28.747) ]
$ perf script
Couldn't decompress data
0x598 [0xe53]: failed to process type: 83 [Operation not permitted]
```
If you remove the explicit `--aio` while keeping compression via `-z` enabled,
then the result file can be parsed. Enabling `--aio` but disabling `-z` also
works as expected.
My understanding so far was that `-z` implies `--aio`, and that there should
be zero semantic difference between `-z` and `-z --aio`. But apparently this
was a misunderstanding on my end.
I suspect that the above issue is related to the recent addition of the
COMPRESSED2 record type, since commands combining both of these flags used to
work fine until very recently.
Cheers
--
Milian Wolff | milian.wolff@kdab.com | Senior Software Engineer
KDAB (Deutschland) GmbH, a KDAB Group company
Tel: +49-30-521325470
KDAB - Trusted Software Excellence
next reply other threads:[~2025-09-10 8:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-10 8:51 Milian Wolff [this message]
2025-09-12 12:31 ` combined usage of `--aio -z` corrupts perf.data files - fallout from COMPRESSED2? Milian Wolff
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=38208379.DOZC079dcN@milian-workstation \
--to=milian.wolff@kdab.com \
--cc=acme@kernel.org \
--cc=ctshao@google.com \
--cc=linux-perf-users@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox