On Thu, Oct 22, 2020 at 3:20 PM Andrey Konovalov <andreyknvl@xxxxxxxxxx> 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> > Link: https://linux-review.googlesource.com/id/I1334dffb69b87d7986fab88a1a039cc3ea764725 Reviewed-by: Dmitry Vyukov <dvyukov@xxxxxxxxxx> > --- > 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 3cd56861eb11..54af79aa8d3f 100644 > --- a/mm/kasan/common.c > +++ b/mm/kasan/common.c > @@ -445,5 +445,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.0.rc1.297.gfa9743e501-goog >
