libbpf-tools: Fix 64-bit format portability - #5549
Open
berringtoni36-commits wants to merge 1 commit into
Open
Conversation
Signed-off-by: 赵文强 <17364305797@163.com>
berringtoni36-commits
requested review from
brendangregg,
chenhengqi,
ekyooo and
yonghong-song
as code owners
August 28, 2026 13:50
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Use the portable integer format macros from <inttypes.h> for 64-bit values in libbpf-tools, and explicitly cast lost-event counters passed to variadic logging functions. This avoids assuming that Linux __u64 is always unsigned long long, which breaks builds on ppc64le where it is unsigned long.
The change covers the libbpf-tools format sites that would otherwise trigger -Werror=format, including the failure reported in #5330.
Testing
Fixes #5330