From: Andrey Konovalov <andreyknvl@gmail.com>
To: Haibo Li <haibo.li@mediatek.com>
Cc: akpm@linux-foundation.org,
angelogioacchino.delregno@collabora.com, dvyukov@google.com,
glider@google.com, jannh@google.com, kasan-dev@googlegroups.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org,
linux-mm@kvack.org, mark.rutland@arm.com, matthias.bgg@gmail.com,
ryabinin.a.a@gmail.com, vincenzo.frascino@arm.com,
xiaoming.yu@mediatek.com
Subject: Re: [PATCH] kasan:fix access invalid shadow address when input is illegal
Date: Fri, 15 Sep 2023 18:53:34 +0200 [thread overview]
Message-ID: <CA+fCnZd0FkKNf1ZQxbXWvNM8NAt=ML+yXu5n4VgLOmhFf9TPfQ@mail.gmail.com> (raw)
In-Reply-To: <20230915094004.113104-1-haibo.li@mediatek.com>
On Fri, Sep 15, 2023 at 11:40 AM 'Haibo Li' via kasan-dev
<kasan-dev@googlegroups.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!
WARNING: multiple messages have this Message-ID (diff)
From: Andrey Konovalov <andreyknvl@gmail.com>
To: Haibo Li <haibo.li@mediatek.com>
Cc: akpm@linux-foundation.org,
angelogioacchino.delregno@collabora.com, dvyukov@google.com,
glider@google.com, jannh@google.com, kasan-dev@googlegroups.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
linux-mediatek@lists.infradead.org, linux-mm@kvack.org,
mark.rutland@arm.com, matthias.bgg@gmail.com,
ryabinin.a.a@gmail.com, vincenzo.frascino@arm.com,
xiaoming.yu@mediatek.com
Subject: Re: [PATCH] kasan:fix access invalid shadow address when input is illegal
Date: Fri, 15 Sep 2023 18:53:34 +0200 [thread overview]
Message-ID: <CA+fCnZd0FkKNf1ZQxbXWvNM8NAt=ML+yXu5n4VgLOmhFf9TPfQ@mail.gmail.com> (raw)
In-Reply-To: <20230915094004.113104-1-haibo.li@mediatek.com>
On Fri, Sep 15, 2023 at 11:40 AM 'Haibo Li' via kasan-dev
<kasan-dev@googlegroups.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!
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-09-15 16:54 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-14 8:08 [PATCH] kasan:fix access invalid shadow address when input is illegal Haibo Li
2023-09-14 8:08 ` Haibo Li
2023-09-14 17:46 ` Andrey Konovalov
2023-09-14 17:46 ` Andrey Konovalov
2023-09-14 18:29 ` Andrew Morton
2023-09-14 18:29 ` Andrew Morton
2023-09-14 20:34 ` Andrey Konovalov
2023-09-14 20:34 ` Andrey Konovalov
2023-09-14 20:40 ` Jann Horn
2023-09-14 20:40 ` Jann Horn
2023-09-15 1:51 ` Andrey Konovalov
2023-09-15 1:51 ` Andrey Konovalov
2023-09-15 2:45 ` Haibo Li
2023-09-15 2:45 ` Haibo Li
2023-09-15 9:40 ` Haibo Li
2023-09-15 9:40 ` Haibo Li
2023-09-15 16:53 ` Andrey Konovalov [this message]
2023-09-15 16:53 ` Andrey Konovalov
2023-09-15 16:50 ` Andrey Konovalov
2023-09-15 16:50 ` Andrey Konovalov
2023-09-15 17:04 ` Jann Horn
2023-09-15 17:04 ` Jann Horn
2023-09-18 8:12 ` Haibo Li
2023-09-18 8:12 ` Haibo Li
2023-09-18 7:25 ` Haibo Li
2023-09-18 7:25 ` Haibo Li
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CA+fCnZd0FkKNf1ZQxbXWvNM8NAt=ML+yXu5n4VgLOmhFf9TPfQ@mail.gmail.com' \
--to=andreyknvl@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=haibo.li@mediatek.com \
--cc=jannh@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-mm@kvack.org \
--cc=mark.rutland@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=ryabinin.a.a@gmail.com \
--cc=vincenzo.frascino@arm.com \
--cc=xiaoming.yu@mediatek.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.