From: Vincenzo Frascino <vincenzo.frascino@arm.com>
To: Mark Rutland <mark.rutland@arm.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kasan-dev@googlegroups.com,
Marco Elver <elver@google.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Branislav Rankov <Branislav.Rankov@arm.com>,
Alexander Potapenko <glider@google.com>,
Evgenii Stepanov <eugenis@google.com>,
Andrey Konovalov <andreyknvl@google.com>,
Andrey Ryabinin <aryabinin@virtuozzo.com>,
Will Deacon <will@kernel.org>, Dmitry Vyukov <dvyukov@google.com>
Subject: Re: [PATCH v3 1/4] kasan, arm64: Add KASAN light mode
Date: Sat, 16 Jan 2021 13:47:08 +0000 [thread overview]
Message-ID: <ba23ab9b-8f49-bdb7-87d8-3eb99ddf54b6@arm.com> (raw)
In-Reply-To: <20210115150811.GA44111@C02TD0UTHF1T.local>
Hi Mark,
On 1/15/21 3:08 PM, Mark Rutland wrote:
> On Fri, Jan 15, 2021 at 12:00:40PM +0000, Vincenzo Frascino wrote:
>> Architectures supported by KASAN HW can provide a light mode of
>> execution. On an MTE enabled arm64 hw for example this can be identified
>> with the asynch mode of execution.
>> In this mode, if a tag check fault occurs, the TFSR_EL1 register is
>> updated asynchronously. The kernel checks the corresponding bits
>> periodically.
>
> What's the expected usage of this relative to prod, given that this has
> to be chosen at boot time? When/where is this expected to be used
> relative to prod mode?
>
IIUC the light mode is meant for low spec devices. I let Andrey comment a bit
more on this topic.
>> diff --git a/arch/arm64/include/asm/memory.h b/arch/arm64/include/asm/memory.h
>> index 18fce223b67b..3a7c5beb7096 100644
>> --- a/arch/arm64/include/asm/memory.h
>> +++ b/arch/arm64/include/asm/memory.h
>> @@ -231,7 +231,7 @@ static inline const void *__tag_set(const void *addr, u8 tag)
>> }
>>
>> #ifdef CONFIG_KASAN_HW_TAGS
>> -#define arch_enable_tagging() mte_enable_kernel()
>> +#define arch_enable_tagging(mode) mte_enable_kernel(mode)
>
> Rather than passing a mode in, I think it'd be better to have:
>
> * arch_enable_tagging_prod()
> * arch_enable_tagging_light()
>
> ... that we can map in the arch code to separate:
>
> * mte_enable_kernel_sync()
> * mte_enable_kernel_async()
>
> ... as by construction that avoids calls with an unhandled mode, and we
> wouldn't need the mode enum kasan_hw_tags_mode...
>
>> +static inline int hw_init_mode(enum kasan_arg_mode mode)
>> +{
>> + switch (mode) {
>> + case KASAN_ARG_MODE_LIGHT:
>> + return KASAN_HW_TAGS_ASYNC;
>> + default:
>> + return KASAN_HW_TAGS_SYNC;
>> + }
>> +}
>
> ... and we can just have a wrapper like this to call either of the two functions directly, i.e.
>
> static inline void hw_enable_tagging_mode(enum kasan_arg_mode mode)
> {
> if (mode == KASAN_ARG_MODE_LIGHT)
> arch_enable_tagging_mode_light();
> else
> arch_enable_tagging_mode_prod();
> }
>
Fine by me, this would remove the need of adding a new enumeration as well and
reflect on the arch code. I would keep "arch_enable_tagging_mode_sync" and
"arch_enable_tagging_mode_async" though to give a clear indication in the KASAN
code of the mode we are setting. I will adapt my code accordingly for v4.
> Thanks,
> Mark.
>
--
Regards,
Vincenzo
next prev parent reply other threads:[~2021-01-16 17:58 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-15 12:00 [PATCH v3 0/4] arm64: ARMv8.5-A: MTE: Add async mode support Vincenzo Frascino
2021-01-15 12:00 ` [PATCH v3 1/4] kasan, arm64: Add KASAN light mode Vincenzo Frascino
2021-01-15 15:08 ` Mark Rutland
2021-01-16 13:47 ` Vincenzo Frascino [this message]
2021-01-16 14:09 ` Andrey Konovalov
2021-01-18 10:24 ` Mark Rutland
2021-01-15 18:59 ` Andrey Konovalov
2021-01-16 13:40 ` Vincenzo Frascino
2021-01-16 13:59 ` Andrey Konovalov
2021-01-16 14:06 ` Vincenzo Frascino
2021-01-15 12:00 ` [PATCH v3 2/4] arm64: mte: Add asynchronous mode support Vincenzo Frascino
2021-01-15 15:13 ` Mark Rutland
2021-01-16 13:49 ` Vincenzo Frascino
2021-01-15 12:00 ` [PATCH v3 3/4] arm64: mte: Enable async tag check fault Vincenzo Frascino
2021-01-15 15:37 ` Mark Rutland
2021-01-18 12:57 ` Catalin Marinas
2021-01-18 13:37 ` Vincenzo Frascino
2021-01-18 14:14 ` Mark Rutland
2021-01-18 14:48 ` Vincenzo Frascino
2021-01-18 15:39 ` Vincenzo Frascino
2021-01-18 15:40 ` Vincenzo Frascino
2021-01-15 12:00 ` [PATCH v3 4/4] arm64: mte: Optimize mte_assign_mem_tag_range() Vincenzo Frascino
2021-01-15 15:45 ` Mark Rutland
2021-01-16 14:22 ` Vincenzo Frascino
2021-01-17 12:27 ` Vincenzo Frascino
2021-01-18 10:41 ` Mark Rutland
2021-01-18 11:00 ` Vincenzo Frascino
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=ba23ab9b-8f49-bdb7-87d8-3eb99ddf54b6@arm.com \
--to=vincenzo.frascino@arm.com \
--cc=Branislav.Rankov@arm.com \
--cc=andreyknvl@google.com \
--cc=aryabinin@virtuozzo.com \
--cc=catalin.marinas@arm.com \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=eugenis@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@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
all inboxes | Powered by JetHome®