Messages in this thread | | | From | Alexander Potapenko <> | Date | Tue, 2 Aug 2022 18:31:23 +0200 | Subject | Re: [PATCH v4 15/45] mm: kmsan: call KMSAN hooks from SLUB code |
| |
On Tue, Jul 12, 2022 at 3:14 PM Marco Elver <elver@google.com> wrote: > > On Fri, 1 Jul 2022 at 16:23, 'Alexander Potapenko' via kasan-dev > <kasan-dev@googlegroups.com> wrote: > > > > In order to report uninitialized memory coming from heap allocations > > KMSAN has to poison them unless they're created with __GFP_ZERO. > > > > It's handy that we need KMSAN hooks in the places where > > init_on_alloc/init_on_free initialization is performed. > > > > In addition, we apply __no_kmsan_checks to get_freepointer_safe() to > > suppress reports when accessing freelist pointers that reside in freed > > objects. > > > > Signed-off-by: Alexander Potapenko <glider@google.com> > > Reviewed-by: Marco Elver <elver@google.com> > > But see comment below. >
> > Remove unnecessary whitespace change. Will do, thanks for catching!
-- Alexander Potapenko Software Engineer
Google Germany GmbH Erika-Mann-Straße, 33 80636 München
Geschäftsführer: Paul Manicle, Liana Sebastian Registergericht und -nummer: Hamburg, HRB 86891 Sitz der Gesellschaft: Hamburg
| |