Currently it says that the memory gets poisoned by page_alloc code. Clarify this by mentioning the specific callback that poisons the memory.
Signed-off-by: Andrey Konovalov <andreyk...@google.com> Reviewed-by: Dmitry Vyukov <dvyu...@google.com> Reviewed-by: Marco Elver <el...@google.com> Link: https://linux-review.googlesource.com/id/I1334dffb69b87d7986fab88a1a039cc3ea764725 --- mm/kasan/common.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/mm/kasan/common.c b/mm/kasan/common.c index 821678a58ac6..42ba64fce8a3 100644 --- a/mm/kasan/common.c +++ b/mm/kasan/common.c @@ -453,5 +453,5 @@ void __kasan_kfree_large(void *ptr, unsigned long ip) { if (ptr != page_address(virt_to_head_page(ptr))) kasan_report_invalid_free(ptr, ip); - /* The object will be poisoned by page_alloc. */ + /* The object will be poisoned by kasan_free_pages(). */ } -- 2.29.2.454.gaff20da3a2-goog
