diff options
| author | Andrii Nakryiko <andrii@kernel.org> | 2022-08-15 17:19:27 -0700 |
|---|---|---|
| committer | Daniel Borkmann <daniel@iogearbox.net> | 2022-08-17 22:42:10 +0200 |
| commit | 813847a31447feba6119df4ee77a7c0c7a77fc72 (patch) | |
| tree | 767299922c7899e6a698bd46f63bcf09c175103c /scripts/bpf_doc.py | |
| parent | libbpf: Fix potential NULL dereference when parsing ELF (diff) | |
| download | linux-813847a31447feba6119df4ee77a7c0c7a77fc72.tar.gz linux-813847a31447feba6119df4ee77a7c0c7a77fc72.zip | |
libbpf: Streamline bpf_attr and perf_event_attr initialization
Make sure that entire libbpf code base is initializing bpf_attr and
perf_event_attr with memset(0). Also for bpf_attr make sure we
clear and pass to kernel only relevant parts of bpf_attr. bpf_attr is
a huge union of independent sub-command attributes, so there is no need
to clear and pass entire union bpf_attr, which over time grows quite
a lot and for most commands this growth is completely irrelevant.
Few cases where we were relying on compiler initialization of BPF UAPI
structs (like bpf_prog_info, bpf_map_info, etc) with `= {};` were
switched to memset(0) pattern for future-proofing.
Signed-off-by: Andrii Nakryiko <andrii@kernel.org>
Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
Acked-by: Hao Luo <haoluo@google.com>
Link: https://lore.kernel.org/bpf/20220816001929.369487-3-andrii@kernel.org
Diffstat (limited to 'scripts/bpf_doc.py')
0 files changed, 0 insertions, 0 deletions
