diff options
author | Alexei Starovoitov <ast@kernel.org> | 2024-10-10 02:32:47 +0300 |
---|---|---|
committer | Alexei Starovoitov <ast@kernel.org> | 2024-10-10 02:32:47 +0300 |
commit | 830b8e49424b15ca469e2a5b162c9ee818a113c6 (patch) | |
tree | 9c608a91d62af4614fd05f8ac7ea1034e5385a35 /tools/perf/scripts/python/exported-sql-viewer.py | |
parent | b24d7f0da6ef5a23456a301eaf51b170f961d4ae (diff) | |
parent | c456f08040589a5096481277c83168a4e7ae7ed7 (diff) | |
download | linux-830b8e49424b15ca469e2a5b162c9ee818a113c6.tar.xz |
Merge branch 'check-the-remaining-info_cnt-before-repeating-btf-fields'
Hou Tao says:
====================
Check the remaining info_cnt before repeating btf fields
From: Hou Tao <houtao1@huawei.com>
Hi,
The patch set adds the missed check again info_cnt when flattening the
array of nested struct. The problem was spotted when developing dynptr
key support for hash map. Patch #1 adds the missed check and patch #2
adds three success test cases and one failure test case for the problem.
Comments are always welcome.
Change Log:
v2:
* patch #1: check info_cnt in btf_repeat_fields()
* patch #2: use a hard-coded number instead of BTF_FIELDS_MAX, because
BTF_FIELDS_MAX is not always available in vmlinux.h (e.g.,
for llvm 17/18)
v1: https://lore.kernel.org/bpf/20240911110557.2759801-1-houtao@huaweicloud.com/T/#t
====================
Link: https://lore.kernel.org/r/20241008071114.3718177-1-houtao@huaweicloud.com
Signed-off-by: Alexei Starovoitov <ast@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/exported-sql-viewer.py')
0 files changed, 0 insertions, 0 deletions