linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
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
Subject: Re: [PATCH v9 1/6] kasan: allow an architecture to disable inline instrumentation
Date: Tue, 1 Dec 2020 17:49:21 +0100	[thread overview]
Message-ID: <c091e596-acfb-2d26-1c27-4388c22988cf@csgroup.eu> (raw)
In-Reply-To: <20201201161632.1234753-2-dja@axtens.net>



Le 01/12/2020 à 17:16, Daniel Axtens a écrit :
> For annoying architectural reasons, it's very difficult to support inline
> instrumentation on powerpc64.
> 
> Add a Kconfig flag to allow an arch to disable inline. (It's a bit
> annoying to be 'backwards', but I'm not aware of any way to have
> an arch force a symbol to be 'n', rather than 'y'.)
> 
> Signed-off-by: Daniel Axtens <dja@axtens.net>
> ---
>   lib/Kconfig.kasan | 4 ++++
>   1 file changed, 4 insertions(+)
> 
> diff --git a/lib/Kconfig.kasan b/lib/Kconfig.kasan
> index 542a9c18398e..31a0b28f6c2b 100644
> --- a/lib/Kconfig.kasan
> +++ b/lib/Kconfig.kasan
> @@ -9,6 +9,9 @@ config HAVE_ARCH_KASAN_SW_TAGS
>   config	HAVE_ARCH_KASAN_VMALLOC
>   	bool
>   
> +config HAVE_ARCH_NO_KASAN_INLINE

Maybe a better name could be: ARCH_DISABLE_KASAN_INLINE

> +	def_bool n
> +
>   config CC_HAS_KASAN_GENERIC
>   	def_bool $(cc-option, -fsanitize=kernel-address)
>   
> @@ -108,6 +111,7 @@ config KASAN_OUTLINE
>   
>   config KASAN_INLINE
>   	bool "Inline instrumentation"
> +	depends on !HAVE_ARCH_NO_KASAN_INLINE
>   	help
>   	  Compiler directly inserts code checking shadow memory before
>   	  memory accesses. This is faster than outline (in some workloads
> 


  reply	other threads:[~2020-12-01 16:49 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 [this message]
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
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=c091e596-acfb-2d26-1c27-4388c22988cf@csgroup.eu \
    --to=christophe.leroy@csgroup.eu \
    --cc=aneesh.kumar@linux.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).