linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrey Konovalov <andreyknvl@gmail.com>
To: Peter Collingbourne <pcc@google.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
	Vincenzo Frascino <vincenzo.frascino@arm.com>,
	 Will Deacon <will@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	 Evgenii Stepanov <eugenis@google.com>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	 Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [PATCH v5 1/2] kasan: split kasan_*enabled() functions into a separate header
Date: Tue, 22 Feb 2022 17:38:34 +0100	[thread overview]
Message-ID: <CA+fCnZc7ytoE8iDWx4HPgcCsDR-jVbjncpC3a_EFRzcH62gTBQ@mail.gmail.com> (raw)
In-Reply-To: <20220219012945.894950-1-pcc@google.com>

On Sat, Feb 19, 2022 at 2:30 AM Peter Collingbourne <pcc@google.com> wrote:
>
> In an upcoming commit we are going to need to call
> kasan_hw_tags_enabled() from arch/arm64/include/asm/mte.h. This
> would create a circular dependency between headers if KASAN_GENERIC
> or KASAN_SW_TAGS is enabled: linux/kasan.h -> linux/pgtable.h ->
> asm/pgtable.h -> asm/mte.h -> linux/kasan.h. Break the cycle
> by introducing a new header linux/kasan-enabled.h with the
> kasan_*enabled() functions that can be included from asm/mte.h.
>
> Link: https://linux-review.googlesource.com/id/I5b0d96c6ed0026fc790899e14d42b2fac6ab568e
> Signed-off-by: Peter Collingbourne <pcc@google.com>
> ---
>  include/linux/kasan-enabled.h | 33 +++++++++++++++++++++++++++++++++
>  include/linux/kasan.h         | 23 +----------------------
>  2 files changed, 34 insertions(+), 22 deletions(-)
>  create mode 100644 include/linux/kasan-enabled.h
>
> diff --git a/include/linux/kasan-enabled.h b/include/linux/kasan-enabled.h
> new file mode 100644
> index 000000000000..4b6615375022
> --- /dev/null
> +++ b/include/linux/kasan-enabled.h
> @@ -0,0 +1,33 @@
> +/* SPDX-License-Identifier: GPL-2.0 */
> +#ifndef _LINUX_KASAN_ENABLED_H
> +#define _LINUX_KASAN_ENABLED_H
> +
> +#ifdef CONFIG_KASAN_HW_TAGS
> +
> +DECLARE_STATIC_KEY_FALSE(kasan_flag_enabled);
> +
> +static __always_inline bool kasan_enabled(void)
> +{
> +       return static_branch_likely(&kasan_flag_enabled);
> +}
> +
> +static inline bool kasan_hw_tags_enabled(void)
> +{
> +       return kasan_enabled();
> +}
> +
> +#else /* CONFIG_KASAN_HW_TAGS */
> +
> +static inline bool kasan_enabled(void)
> +{
> +       return IS_ENABLED(CONFIG_KASAN);
> +}
> +
> +static inline bool kasan_hw_tags_enabled(void)
> +{
> +       return false;
> +}
> +
> +#endif /* CONFIG_KASAN_HW_TAGS */
> +
> +#endif /* LINUX_KASAN_ENABLED_H */
> diff --git a/include/linux/kasan.h b/include/linux/kasan.h
> index 4a45562d8893..b6a93261c92a 100644
> --- a/include/linux/kasan.h
> +++ b/include/linux/kasan.h
> @@ -3,6 +3,7 @@
>  #define _LINUX_KASAN_H
>
>  #include <linux/bug.h>
> +#include <linux/kasan-enabled.h>
>  #include <linux/kernel.h>
>  #include <linux/static_key.h>
>  #include <linux/types.h>
> @@ -83,33 +84,11 @@ static inline void kasan_disable_current(void) {}
>
>  #ifdef CONFIG_KASAN_HW_TAGS
>
> -DECLARE_STATIC_KEY_FALSE(kasan_flag_enabled);
> -
> -static __always_inline bool kasan_enabled(void)
> -{
> -       return static_branch_likely(&kasan_flag_enabled);
> -}
> -
> -static inline bool kasan_hw_tags_enabled(void)
> -{
> -       return kasan_enabled();
> -}
> -
>  void kasan_alloc_pages(struct page *page, unsigned int order, gfp_t flags);
>  void kasan_free_pages(struct page *page, unsigned int order);
>
>  #else /* CONFIG_KASAN_HW_TAGS */
>
> -static inline bool kasan_enabled(void)
> -{
> -       return IS_ENABLED(CONFIG_KASAN);
> -}
> -
> -static inline bool kasan_hw_tags_enabled(void)
> -{
> -       return false;
> -}
> -
>  static __always_inline void kasan_alloc_pages(struct page *page,
>                                               unsigned int order, gfp_t flags)
>  {
> --
> 2.35.1.473.g83b2b277ed-goog
>

Reviewed-by: Andrey Konovalov <andreyknvl@gmail.com>


  parent reply	other threads:[~2022-02-22 16:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-19  1:29 Peter Collingbourne
2022-02-19  1:29 ` [PATCH v5 2/2] arm64: mte: avoid clearing PSTATE.TCO on entry unless necessary Peter Collingbourne
2022-02-22 16:38 ` Andrey Konovalov [this message]
2022-02-22 22:38 ` [PATCH v5 1/2] kasan: split kasan_*enabled() functions into a separate header Will Deacon

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+fCnZc7ytoE8iDWx4HPgcCsDR-jVbjncpC3a_EFRzcH62gTBQ@mail.gmail.com \
    --to=andreyknvl@gmail.com \
    --cc=catalin.marinas@arm.com \
    --cc=eugenis@google.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-mm@kvack.org \
    --cc=mark.rutland@arm.com \
    --cc=pcc@google.com \
    --cc=vincenzo.frascino@arm.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