diff options
| author | Jann Horn <jannh@google.com> | 2026-08-12 20:56:38 +0200 |
|---|---|---|
| committer | Peter Zijlstra <peterz@infradead.org> | 2026-10-01 14:00:40 +0200 |
| commit | 5b5224220747029bbaee8ab851cc6c599c48eded (patch) | |
| tree | b81a5ddcb45c9634052d8c6b89e357f12e514bfb /tools/perf/scripts/python/task-analyzer.py | |
| parent | 72d3fcf802c45d00b300f25b848a93c3a2bd7c7e (diff) | |
refcount: Use CONFIG_BUG_ON_DATA_CORRUPTION for UAF-related errors
Some refcount issues are not necessarily associated with memory corruption,
but REFCOUNT_ADD_UAF suggests that a UAF either just happened or is about
to happen.
REFCOUNT_SUB_UAF is also an indicator that reference counting is wrong, and
suggests (less strongly) that a UAF access might have happened recently.
In these cases, BUG() is appropriate if CONFIG_BUG_ON_DATA_CORRUPTION is
set.
Signed-off-by: Jann Horn <jannh@google.com>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Acked-by: Will Deacon <will@kernel.org>
Link: https://patch.msgid.link/20260812-refcount-bug-on-data-corruption-v1-1-c6da63566101@google.com
Diffstat (limited to 'tools/perf/scripts/python/task-analyzer.py')
0 files changed, 0 insertions, 0 deletions