-
Notifications
You must be signed in to change notification settings - Fork 132
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bpftool: Using the right format specifiers #8644
base: bpf-next_base
Are you sure you want to change the base?
Conversation
Upstream branch: 79d93c8 |
At least one diff in series https://patchwork.kernel.org/project/netdevbpf/list/?series=942309 expired. Closing PR. |
Upstream branch: a68894a |
ca34fc3
to
adf82db
Compare
474f6ed
to
44c3a1d
Compare
Upstream branch: be741c7 |
adf82db
to
bde7861
Compare
44c3a1d
to
720c696
Compare
This commit adds the -Wformat-signedness compiler flag to detect and prevent printf format errors, where signed or unsigned types are mismatched with format specifiers. This helps to catch potential issues at compile-time, ensuring that our code is more robust and reliable. With this flag, the compiler will now warn about incorrect format strings, such as using %d with unsigned types or %u with signed types. Signed-off-by: Jiayuan Chen <[email protected]>
Fixed some formatting specifiers errors, such as using %d for int and %u for unsigned int, as well as other byte-length types. Perform type cast using the type derived from the data type itself, for example, if it's originally an int, it will be cast to unsigned int if forced to unsigned. Signed-off-by: Jiayuan Chen <[email protected]>
Upstream branch: 46d38f4 |
bde7861
to
f28b5e4
Compare
Pull request for series with
subject: bpftool: Using the right format specifiers
version: 1
url: https://patchwork.kernel.org/project/netdevbpf/list/?series=942309