From: Mark Rutland <mark.rutland@arm.com>
To: linux-arm-kernel@lists.infradead.org
Cc: andreyknvl@gmail.com, catalin.marinas@arm.com,
dvyukov@google.com, glider@google.com,
linux-kernel@vger.kernel.org, mark.rutland@arm.com,
ryabinin.a.a@gmail.com, will@kernel.org
Subject: [PATCH 0/3] arm64: kasan: log potential KASAN shadow aliases
Date: Thu, 2 Dec 2021 11:27:28 +0000 [thread overview]
Message-ID: <20211202112731.3346975-1-mark.rutland@arm.com> (raw)
When using KASAN_GENERIC or KASAN_SW_TAGS, many representable pointer
values (e.g. NULL) don't have a legitimate shadow address. If KASAN
instrumentation attempts to access the shadow for such pointers, it will
fault on an unusual-looking address, e.g.
| Unable to handle kernel paging request at virtual address dfff800000000001
To make this easier to debug, this series makes the arm64 fault handling
code log the corresponding memory range for potential shadow acceses,
e.g.
| Unable to handle kernel paging request at virtual address dfff800000000001
| Possible KASAN shadow access for range [0000000000000008..000000000000000f]
Thanks,
Mark.
Mark Rutland (3):
kasan: move kasan_shadow_to_mem() to shared header
arm64: mm: use die_kernel_fault() in do_mem_abort()
arm64: mm: log potential KASAN shadow alias
arch/arm64/mm/fault.c | 13 ++++++++-----
include/linux/kasan.h | 6 ++++++
mm/kasan/kasan.h | 6 ------
3 files changed, 14 insertions(+), 11 deletions(-)
--
2.30.2
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2021-12-02 11:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-02 11:27 Mark Rutland [this message]
2021-12-02 11:27 ` [PATCH 1/3] kasan: move kasan_shadow_to_mem() to shared header Mark Rutland
2021-12-02 11:27 ` [PATCH 2/3] arm64: mm: use die_kernel_fault() in do_mem_abort() Mark Rutland
2021-12-02 11:27 ` [PATCH 3/3] arm64: mm: log potential KASAN shadow alias Mark Rutland
2021-12-02 16:20 ` Andrey Konovalov
2021-12-02 16:30 ` Mark Rutland
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=20211202112731.3346975-1-mark.rutland@arm.com \
--to=mark.rutland@arm.com \
--cc=andreyknvl@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ryabinin.a.a@gmail.com \
--cc=will@kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox