[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+fCnZfuaovc4fk6Z+p1haLk7iemgtpF522sej3oWYARhBYYUQ@mail.gmail.com>
Date: Fri, 15 Sep 2023 18:50:48 +0200
From: Andrey Konovalov <andreyknvl@...il.com>
To: Haibo Li <haibo.li@...iatek.com>, jannh@...gle.com
Cc: akpm@...ux-foundation.org, angelogioacchino.delregno@...labora.com,
dvyukov@...gle.com, glider@...gle.com, kasan-dev@...glegroups.com,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-mediatek@...ts.infradead.org, linux-mm@...ck.org,
mark.rutland@....com, matthias.bgg@...il.com,
ryabinin.a.a@...il.com, vincenzo.frascino@....com,
xiaoming.yu@...iatek.com
Subject: Re: [PATCH] kasan:fix access invalid shadow address when input is illegal
On Fri, Sep 15, 2023 at 4:46 AM 'Haibo Li' via kasan-dev
<kasan-dev@...glegroups.com> wrote:
>
> The patch checks each shadow address,so it introduces extra overhead.
Ack. Could still be fine, depends on the overhead.
But if the message printed by kasan_non_canonical_hook is good enough
for your use case, I would rather stick to that.
> Now kasan_non_canonical_hook only works for CONFIG_KASAN_INLINE.
>
> And CONFIG_KASAN_OUTLINE is set in my case.
>
> Is it possible to make kasan_non_canonical_hook works for both
> INLINE and OUTLINE by simply remove the "#ifdef CONFIG_KASAN_INLINE"?
Yes, it should just work if you remove the ifdefs in mm/kasan/report.c
and in include/linux/kasan.h.
Jann, do you have any objections to enabling kasan_non_canonical_hook
for the outline mode too?
> Since kasan_non_canonical_hook is only used after kernel fault,it
> is better if there is no limit.
Powered by blists - more mailing lists