On Tue, Nov 10, 2020 at 11:20PM +0100, Andrey Konovalov wrote: > 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 <andreyknvl@xxxxxxxxxx> > Reviewed-by: Dmitry Vyukov <dvyukov@xxxxxxxxxx> > Link: https://linux-review.googlesource.com/id/I1334dffb69b87d7986fab88a1a039cc3ea764725 > --- > mm/kasan/common.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) Reviewed-by: Marco Elver <elver@xxxxxxxxxx> > diff --git a/mm/kasan/common.c b/mm/kasan/common.c > index 40ff3ce07a76..4360292ad7f3 100644 > --- a/mm/kasan/common.c > +++ b/mm/kasan/common.c > @@ -436,5 +436,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.222.g5d2a92d10f8-goog >
