diff options
| author | Arnaldo Carvalho de Melo <acme@redhat.com> | 2026-04-08 20:32:01 +0300 |
|---|---|---|
| committer | Namhyung Kim <namhyung@kernel.org> | 2026-04-09 05:21:05 +0300 |
| commit | 7507abd16a05e8b191ed7bed69e075b23111c401 (patch) | |
| tree | b722e640d1dc762cb638498d601ae4c4ca71fb49 /tools/lib/python/feat/parse_features.py | |
| parent | fc32ae6df83d78145391bfdaf0e213babad8e93f (diff) | |
| download | linux-7507abd16a05e8b191ed7bed69e075b23111c401.tar.xz | |
perf header: Do validation of perf.data HEADER_CPU_DOMAIN_INFO
As suggested in an unrelated sashiko review:
https://sashiko.dev/#/patchset/20260407195145.2372104-1-acme%40kernel.org
"
Could a malformed perf.data file provide out-of-bounds values for cpu and
domain?
These variables are read directly from the file and used as indices for
cd_map and cd_map[cpu]->domains without any validation against
env->nr_cpus_avail or max_sched_domains.
Similar to the issue above, this is an existing lack of validation that
becomes apparent when looking at the allocation boundaries.
"
Validate it.
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
Signed-off-by: Namhyung Kim <namhyung@kernel.org>
Diffstat (limited to 'tools/lib/python/feat/parse_features.py')
0 files changed, 0 insertions, 0 deletions