Messages in this thread |  | | From | Andrey Konovalov <> | Date | Mon, 20 Dec 2021 22:35:19 +0100 | Subject | Re: [PATCH mm v3 26/38] kasan, vmalloc: don't unpoison VM_ALLOC pages before mapping |
| |
On Thu, Dec 16, 2021 at 8:08 PM Alexander Potapenko <glider@google.com> wrote: > > On Mon, Dec 13, 2021 at 10:54 PM <andrey.konovalov@linux.dev> wrote: > > > > From: Andrey Konovalov <andreyknvl@google.com> > > > > Make KASAN unpoison vmalloc mappings after that have been mapped in > > when it's possible: for vmalloc() (indentified via VM_ALLOC) and > > vm_map_ram(). > > The subject says "don't unpoison VM_ALLOC pages", whereas the > description says "unpoison VM_ALLOC pages", or am I missing something?
Yes :) The title says "don't unpoison *before*", and the body says "unpoison *after*".
I'll reword the changelog in v4 to make it less confusing.
Thanks!
|  |