[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+fCnZd0FkKNf1ZQxbXWvNM8NAt=ML+yXu5n4VgLOmhFf9TPfQ@mail.gmail.com>
Date: Fri, 15 Sep 2023 18:53:34 +0200
From: Andrey Konovalov <andreyknvl@...il.com>
To: Haibo Li <haibo.li@...iatek.com>
Cc: akpm@...ux-foundation.org, angelogioacchino.delregno@...labora.com,
dvyukov@...gle.com, glider@...gle.com, jannh@...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 11:40 AM 'Haibo Li' via kasan-dev
<kasan-dev@...glegroups.com> wrote:
>
> I checked inline mode just now.kasan_non_canonical_hook can print
> something like below:
>
> Unable to handle kernel paging request at virtual address ffffffb80aaaaaaa
> KASAN: maybe wild-memory-access in range [0xffffff80aaaaaaa0-0xffffff80aaaaaaaf]
>
> When addr < KASAN_SHADOW_OFFSET meets,the original addr_has_metadata should return false
> and trigger kasan_report in kasan_check_range.
It should, but I don't think it always does. But if it works for you,
let's leave it at that. I'll double check why it failed for me later.
Thanks!
Powered by blists - more mailing lists