From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Daniel Axtens <dja@axtens.net>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linuxppc-dev@lists.ozlabs.org, kasan-dev@googlegroups.com,
christophe.leroy@c-s.fr, aneesh.kumar@linux.ibm.com,
bsingharora@gmail.com
Cc: "Aneesh Kumar K . V" <aneesh.kumar@linux.vnet.ibm.com>
Subject: Re: [PATCH v9 2/6] kasan: allow architectures to provide an outline readiness check
Date: Tue, 1 Dec 2020 17:53:02 +0100 [thread overview]
Message-ID: <bc92b30f-f087-ced6-cf00-a62370eae733@csgroup.eu> (raw)
In-Reply-To: <20201201161632.1234753-3-dja@axtens.net>
Le 01/12/2020 à 17:16, Daniel Axtens a écrit :
> Allow architectures to define a kasan_arch_is_ready() hook that bails
> out of any function that's about to touch the shadow unless the arch
> says that it is ready for the memory to be accessed. This is fairly
> uninvasive and should have a negligible performance penalty.
>
> This will only work in outline mode, so an arch must specify
> HAVE_ARCH_NO_KASAN_INLINE if it requires this.
>
> Cc: Balbir Singh <bsingharora@gmail.com>
> Cc: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
> Signed-off-by: Christophe Leroy <christophe.leroy@c-s.fr>
Did I signed that off one day ? I can't remember.
Please update my email address, and maybe change it to a Suggested-by: ? I think the first
Signed-off-by: has to be the author of the patch.
> Signed-off-by: Daniel Axtens <dja@axtens.net>
>
> --
>
> I discuss the justfication for this later in the series. Also,
> both previous RFCs for ppc64 - by 2 different people - have
> needed this trick! See:
> - https://lore.kernel.org/patchwork/patch/592820/ # ppc64 hash series
> - https://patchwork.ozlabs.org/patch/795211/ # ppc radix series
> ---
> include/linux/kasan.h | 4 ++++
> mm/kasan/common.c | 10 ++++++++++
> mm/kasan/generic.c | 3 +++
> 3 files changed, 17 insertions(+)
>
> diff --git a/include/linux/kasan.h b/include/linux/kasan.h
> index 30d343b4a40a..3df66fdf6662 100644
> --- a/include/linux/kasan.h
> +++ b/include/linux/kasan.h
> @@ -20,6 +20,10 @@ struct kunit_kasan_expectation {
> bool report_found;
> };
>
> +#ifndef kasan_arch_is_ready
> +static inline bool kasan_arch_is_ready(void) { return true; }
> +#endif
> +
> extern unsigned char kasan_early_shadow_page[PAGE_SIZE];
> extern pte_t kasan_early_shadow_pte[PTRS_PER_PTE];
> extern pmd_t kasan_early_shadow_pmd[PTRS_PER_PMD];
> diff --git a/mm/kasan/common.c b/mm/kasan/common.c
> index 950fd372a07e..ba7744d3e319 100644
> --- a/mm/kasan/common.c
> +++ b/mm/kasan/common.c
> @@ -117,6 +117,9 @@ void kasan_poison_shadow(const void *address, size_t size, u8 value)
> {
> void *shadow_start, *shadow_end;
>
> + if (!kasan_arch_is_ready())
> + return;
> +
> /*
> * Perform shadow offset calculation based on untagged address, as
> * some of the callers (e.g. kasan_poison_object_data) pass tagged
> @@ -134,6 +137,9 @@ void kasan_unpoison_shadow(const void *address, size_t size)
> {
> u8 tag = get_tag(address);
>
> + if (!kasan_arch_is_ready())
> + return;
> +
> /*
> * Perform shadow offset calculation based on untagged address, as
> * some of the callers (e.g. kasan_unpoison_object_data) pass tagged
> @@ -406,6 +412,10 @@ static bool __kasan_slab_free(struct kmem_cache *cache, void *object,
> if (unlikely(cache->flags & SLAB_TYPESAFE_BY_RCU))
> return false;
>
> + /* We can't read the shadow byte if the arch isn't ready */
> + if (!kasan_arch_is_ready())
> + return false;
> +
> shadow_byte = READ_ONCE(*(s8 *)kasan_mem_to_shadow(object));
> if (shadow_invalid(tag, shadow_byte)) {
> kasan_report_invalid_free(tagged_object, ip);
> diff --git a/mm/kasan/generic.c b/mm/kasan/generic.c
> index 248264b9cb76..e87404026b2b 100644
> --- a/mm/kasan/generic.c
> +++ b/mm/kasan/generic.c
> @@ -169,6 +169,9 @@ static __always_inline bool check_memory_region_inline(unsigned long addr,
> size_t size, bool write,
> unsigned long ret_ip)
> {
> + if (!kasan_arch_is_ready())
> + return true;
> +
> if (unlikely(size == 0))
> return true;
>
>
next prev parent reply other threads:[~2020-12-01 16:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-01 16:16 [PATCH v9 0/6] KASAN for powerpc64 radix Daniel Axtens
2020-12-01 16:16 ` [PATCH v9 1/6] kasan: allow an architecture to disable inline instrumentation Daniel Axtens
2020-12-01 16:49 ` Christophe Leroy
2020-12-01 16:16 ` [PATCH v9 2/6] kasan: allow architectures to provide an outline readiness check Daniel Axtens
2020-12-01 16:53 ` Christophe Leroy [this message]
2020-12-01 16:16 ` [PATCH v9 3/6] kasan: define and use MAX_PTRS_PER_* for early shadow tables Daniel Axtens
2020-12-01 16:54 ` Christophe Leroy
2020-12-01 16:16 ` [PATCH v9 4/6] kasan: Document support on 32-bit powerpc Daniel Axtens
2020-12-01 16:56 ` Christophe Leroy
2020-12-01 16:16 ` [PATCH v9 5/6] powerpc/mm/kasan: rename kasan_init_32.c to init_32.c Daniel Axtens
2020-12-01 16:56 ` Christophe Leroy
2020-12-01 16:16 ` [PATCH v9 6/6] powerpc: Book3S 64-bit outline-only KASAN support Daniel Axtens
2020-12-01 17:26 ` Christophe Leroy
2021-02-03 11:46 ` Daniel Axtens
2020-12-02 15:11 ` [PATCH v9 0/6] KASAN for powerpc64 radix Andrey Konovalov
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=bc92b30f-f087-ced6-cf00-a62370eae733@csgroup.eu \
--to=christophe.leroy@csgroup.eu \
--cc=aneesh.kumar@linux.ibm.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=bsingharora@gmail.com \
--cc=christophe.leroy@c-s.fr \
--cc=dja@axtens.net \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).