From: <matteo.bertolino@huawei.com>
To: <linux-trace-devel@vger.kernel.org>
Cc: <rostedt@goodmis.org>,
"Matteo Bertolino (Huawei Technologies France)"
<matteo.bertolino@huawei.com>
Subject: [PATCH] trace-cmd: fixing description of a field in trace-cmd.dat.v7.5.txt doc
Date: Wed, 29 Jun 2022 18:18:45 +0200 [thread overview]
Message-ID: <20220629161845.2432-1-matteo.bertolino@huawei.com> (raw)
From: "Matteo Bertolino (Huawei Technologies France)" <matteo.bertolino@huawei.com>
Paragraph "Format of Section Header" states to write the size of a section on 4 bytes, but the actual size is 8 bytes (long long unsigned int).
Submitted bug: https://bugzilla.kernel.org/show_bug.cgi?id=216185
Signed-off-by: Matteo Bertolino (Huawei Technologies France) <matteo.bertolino@huawei.com>
---
Documentation/trace-cmd/trace-cmd.dat.v7.5.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/trace-cmd/trace-cmd.dat.v7.5.txt b/Documentation/trace-cmd/trace-cmd.dat.v7.5.txt
index e5bcac7..b19d284 100644
--- a/Documentation/trace-cmd/trace-cmd.dat.v7.5.txt
+++ b/Documentation/trace-cmd/trace-cmd.dat.v7.5.txt
@@ -71,7 +71,7 @@ FORMAT OF THE SECTION HEADER
<2 bytes> unsigned short integer, section flags:
1 = the section is compressed.
<4 bytes> ID of a string, description of the section.
- <4 bytes> unsigned integer, size of the section in the file.
+ <8 bytes> long long unsigned integer, size of the section in the file.
If the section is compressed, the above is the compressed size.
The section must be uncompressed on reading. The described format of
--
2.35.1.windows.2
Hello, this is my first (little) contribution!
Please be nice :-)
Matteo
next reply other threads:[~2022-06-29 16:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-29 16:18 matteo.bertolino [this message]
2022-07-08 19:46 ` [PATCH] trace-cmd: fixing description of a field in trace-cmd.dat.v7.5.txt doc Steven Rostedt
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=20220629161845.2432-1-matteo.bertolino@huawei.com \
--to=matteo.bertolino@huawei.com \
--cc=linux-trace-devel@vger.kernel.org \
--cc=rostedt@goodmis.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;
as well as URLs for NNTP newsgroup(s).