Bug 212193 - KASAN: better invalid-free report header
Summary: KASAN: better invalid-free report header
Status: RESOLVED CODE_FIX
Alias: None
Product: Memory Management
Classification: Unclassified
Component: Sanitizers (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: MM/Sanitizers virtual assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-03-09 15:43 UTC by Andrey Konovalov
Modified: 2022-08-30 20:56 UTC (History)
1 user (show)

See Also:
Kernel Version: upstream
Subsystem:
Regression: No
Bisected commit-id:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Andrey Konovalov 2021-03-09 15:43:23 UTC 
Currently, KASAN describes all invalid-free/double-free bugs as "double-free or invalid-free". This is redundant. KASAN should either use "invalid-free" for all of such bugs, or use "double-free" when a double-free is a more likely cause (the address that's being freed points to the start of an object) and use "invalid-free" otherwise.
Note You need to log in before you can comment on or make changes to this bug.