diff options
| author | Kumar Kartikeya Dwivedi <memxor@gmail.com> | 2026-07-11 01:49:39 +0200 |
|---|---|---|
| committer | Kumar Kartikeya Dwivedi <memxor@gmail.com> | 2026-07-12 01:52:55 +0200 |
| commit | 25935519f78be63048f4a964e15be48c83ba7dc2 (patch) | |
| tree | 6d7bf10872e1ec84e4e9c896b4fa4424ed30b6b6 /tools/perf/scripts/python/bin/stackcollapse-record | |
| parent | 77f02c9926e1d58f418a705ee4ecc6975721e117 (diff) | |
| parent | 6267b835286eb552298f22d9e4045b55c3272985 (diff) | |
Merge branch 'bpf-require-an-owned-cpumask-for-bpf_cpumask_populate'
Nicholas Dudar says:
====================
bpf: require an owned cpumask for bpf_cpumask_populate()
bpf_cpumask_populate() writes its destination with bitmap_copy() but
types it as struct cpumask *, so the verifier accepts a borrowed,
read-only cpumask (for example from scx_bpf_get_online_cpumask()) as a
writable destination. Fix it and add a selftest for coverage.
Changelog:
----------
v2 -> v3 (v1/v2 were a private report to security@kernel.org)
* Split the fix and selftest into separate patches.
* Target bpf-next instead of bpf.
====================
Link: https://patch.msgid.link/20260709182800.2037938-1-main.kalliope@gmail.com
Signed-off-by: Kumar Kartikeya Dwivedi <memxor@gmail.com>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-record')
0 files changed, 0 insertions, 0 deletions
