From: Will Deacon <will@kernel.org>
To: Andrey Konovalov <andreyknvl@gmail.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Vincenzo Frascino <vincenzo.frascino@arm.com>,
Peter Collingbourne <pcc@google.com>
Cc: kernel-team@android.com, Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org,
Evgenii Stepanov <eugenis@google.com>,
linux-mm@kvack.org
Subject: Re: [PATCH v5 1/2] kasan: split kasan_*enabled() functions into a separate header
Date: Tue, 22 Feb 2022 22:38:04 +0000 [thread overview]
Message-ID: <164556652455.3187586.10103072855391901269.b4-ty@kernel.org> (raw)
In-Reply-To: <20220219012945.894950-1-pcc@google.com>
On Fri, 18 Feb 2022 17:29:44 -0800, Peter Collingbourne 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.
>
> [...]
Applied to arm64 (for-next/mte), thanks!
[1/2] kasan: split kasan_*enabled() functions into a separate header
https://git.kernel.org/arm64/c/f9b5e46f4097
[2/2] arm64: mte: avoid clearing PSTATE.TCO on entry unless necessary
https://git.kernel.org/arm64/c/38ddf7dafaea
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2022-02-22 22: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 ` [PATCH v5 1/2] kasan: split kasan_*enabled() functions into a separate header Andrey Konovalov
2022-02-22 22:38 ` Will Deacon [this message]
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=164556652455.3187586.10103072855391901269.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=andreyknvl@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=eugenis@google.com \
--cc=kernel-team@android.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 \
/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