[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CA+fCnZcSAzQ8Lk8ZqH0bv0K=Ern8aZr+=cTSzFJeE0uYMVTxmw@mail.gmail.com>
Date: Mon, 13 Dec 2021 22:57:33 +0100
From: Andrey Konovalov <andreyknvl@...il.com>
To: Vincenzo Frascino <vincenzo.frascino@....com>
Cc: andrey.konovalov@...ux.dev, Marco Elver <elver@...gle.com>,
Alexander Potapenko <glider@...gle.com>,
Catalin Marinas <catalin.marinas@....com>,
Peter Collingbourne <pcc@...gle.com>,
Dmitry Vyukov <dvyukov@...gle.com>,
Andrey Ryabinin <ryabinin.a.a@...il.com>,
kasan-dev <kasan-dev@...glegroups.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Linux Memory Management List <linux-mm@...ck.org>,
Will Deacon <will@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>,
Evgenii Stepanov <eugenis@...gle.com>,
LKML <linux-kernel@...r.kernel.org>,
Andrey Konovalov <andreyknvl@...gle.com>
Subject: Re: [PATCH v2 28/34] kasan, vmalloc: add vmalloc support to HW_TAGS
On Mon, Dec 13, 2021 at 4:34 PM Vincenzo Frascino
<vincenzo.frascino@....com> wrote:
>
> Hi Andrey,
>
> On 12/6/21 9:44 PM, andrey.konovalov@...ux.dev wrote:
> > From: Andrey Konovalov <andreyknvl@...gle.com>
> >
> > This patch adds vmalloc tagging support to HW_TAGS KASAN.
> >
>
> Can we reorganize the patch description in line with what I commented on patch 24?
Hi Vincenzo,
Done in v3.
> > void * __must_check __kasan_unpoison_vmalloc(const void *start,
> > - unsigned long size);
> > + unsigned long size,
> > + bool vm_alloc, bool init);
> > static __always_inline void * __must_check kasan_unpoison_vmalloc(
> > - const void *start, unsigned long size)
> > + const void *start, unsigned long size,
> > + bool vm_alloc, bool init)
>
> Can we replace booleans with enumerations? It should make the code clearer on
> the calling site.
I think we can add a single argument for named flags to improve
readability. Done in v3.
> With these changes:
>
> Signed-off-by: Vincenzo Frascino <vincenzo.frascino@....com>
Thanks!
Powered by blists - more mailing lists