[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAAeHK+yV_w3KKWg1bY-Kk=QGGR-=yT=9Ez-XOchY6XOA+h4T3Q@mail.gmail.com>
Date: Thu, 21 Jan 2021 13:27:08 +0100
From: Andrey Konovalov <andreyknvl@...gle.com>
To: Vincenzo Frascino <vincenzo.frascino@....com>
Cc: Catalin Marinas <catalin.marinas@....com>,
LKML <linux-kernel@...r.kernel.org>,
kasan-dev <kasan-dev@...glegroups.com>,
Leon Romanovsky <leonro@...lanox.com>,
Alexander Potapenko <glider@...gle.com>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>,
Andrey Ryabinin <aryabinin@...tuozzo.com>,
Dmitry Vyukov <dvyukov@...gle.com>
Subject: Re: [PATCH] kasan: Add explicit preconditions to kasan_report()
On Thu, Jan 21, 2021 at 12:30 PM Vincenzo Frascino
<vincenzo.frascino@....com> wrote:
>
> Hi Andrey,
>
> On 1/19/21 8:56 PM, Andrey Konovalov wrote:
> >> return (is_vmalloc_addr(addr) || virt_addr_valid(addr));
> > Do we need is_vmalloc_addr()? As we don't yet have vmalloc support for HW_TAGS.
>
> It is not necessary but it does not hurt, since we are going to add vmalloc
> anyway at some point, I would keep it here.
OK, let's keep it.
Powered by blists - more mailing lists