From: Catalin Marinas <catalin.marinas@arm.com>
To: Joey Gouly <joey.gouly@arm.com>
Cc: linux-arm-kernel@lists.infradead.org, nd@arm.com,
mark.rutland@arm.com, robin.murphy@arm.com, will@kernel.org
Subject: Re: [PATCH v2 0/3] Import Arm Optimized Routines str{n}cmp functions
Date: Tue, 1 Mar 2022 15:02:56 +0000 [thread overview]
Message-ID: <Yh41oAVgZwwa/v3a@arm.com> (raw)
In-Reply-To: <20220301101435.19327-1-joey.gouly@arm.com>
On Tue, Mar 01, 2022 at 10:14:32AM +0000, Joey Gouly wrote:
> The previous str{n}cmp routines were not MTE safe, so were disabled in:
> 59a68d413808 ("arm64: Mitigate MTE issues with str{n}cmp()")
>
> The Arm Optimized Routines repository recently merged [1] their strcmp.S and
> strcmp-mte.S files into a single file that is MTE safe.
>
> Therefore we can import these new MTE safe functions and remove the workaround.
>
> I did some light boot tests using QEMU.
>
> Changes since v1 [2]:
> - Rebased onto v5.17-rc3 (Asked for by Will [3])
> - Clarified the license in the commit message
> - Added Mark's acks
For the series:
Acked-by: Catalin Marinas <catalin.marinas@arm.com>
--
Catalin
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-03-01 15:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 10:14 [PATCH v2 0/3] Import Arm Optimized Routines str{n}cmp functions Joey Gouly
2022-03-01 10:14 ` [PATCH v2 1/3] arm64: lib: Import latest version of Arm Optimized Routines' strcmp Joey Gouly
2022-03-01 10:14 ` [PATCH v2 2/3] arm64: lib: Import latest version of Arm Optimized Routines' strncmp Joey Gouly
2022-03-01 10:14 ` [PATCH v2 3/3] Revert "arm64: Mitigate MTE issues with str{n}cmp()" Joey Gouly
2022-03-01 15:02 ` Catalin Marinas [this message]
2022-03-07 22:03 ` [PATCH v2 0/3] Import Arm Optimized Routines str{n}cmp functions 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=Yh41oAVgZwwa/v3a@arm.com \
--to=catalin.marinas@arm.com \
--cc=joey.gouly@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=nd@arm.com \
--cc=robin.murphy@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.