From: Mark Rutland <mark.rutland@arm.com>
To: Joey Gouly <joey.gouly@arm.com>
Cc: linux-arm-kernel@lists.infradead.org, nd@arm.com,
catalin.marinas@arm.com, robin.murphy@arm.com, will@kernel.org
Subject: Re: [PATCH v1 0/3] Import Arm Optimized Routines str{n}cmp functions
Date: Wed, 16 Feb 2022 16:30:26 +0000 [thread overview]
Message-ID: <Yg0mouX04hSRt/r4@lakrids> (raw)
In-Reply-To: <20220215170723.21266-1-joey.gouly@arm.com>
On Tue, Feb 15, 2022 at 05:07:20PM +0000, Joey Gouly wrote:
> Hi all,
Hi,
> 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.
Nice!
As as minor thing, on the two import patches, I think we should be more
explicit about what's going on with licensing, so that it's clear the
license change relative to upstream is intended and legitimate.
For example, in commit:
758602c04409d8c5 ("arm64: Import latest version of Cortex Strings' strcmp")
We had a note in the commit message:
| Note that for simplicity Arm have chosen to contribute this code
| to Linux under GPLv2 rather than the original MIT license.
... and I reckon it's worth being slightly more explicit, e.g.
| Note that for simplicity Arm have chosen to contribute this code
| to Linux under GPLv2 rather than the original MIT license. Arm is the
| sole copyright holder for this code.
That was previously confirmed at:
https://lore.kernel.org/linux-arm-kernel/20210526101723.GA3806@C02TD0UTHF1T.local/
So with that latter wording added to the import patches:
Acked-by: Mark Rutland <mark.rutland@arm.com>
As a heads-up, I believe this will conflict with changes I'm making to
the way symbol aliasing works:
https://lore.kernel.org/lkml/20220216162229.1076788-1-mark.rutland@arm.com/
... and I reckon we need to fix that conflict in the arm64 tree, either
as a merge resolution or rebasing this atop my series.
Thanks,
Mark.
>
> Thanks,
> Joey
>
> [1] https://github.com/ARM-software/optimized-routines/commit/7b91c3cdb12b023004cb4dda30a1aa3424329ce6
>
> Joey Gouly (3):
> arm64: lib: Import latest version of Arm Optimized Routines' strcmp
> arm64: lib: Import latest version of Arm Optimized Routines' strncmp
> Revert "arm64: Mitigate MTE issues with str{n}cmp()"
>
> arch/arm64/include/asm/assembler.h | 5 -
> arch/arm64/include/asm/string.h | 2 -
> arch/arm64/lib/strcmp.S | 240 +++++++++++++++--------------
> arch/arm64/lib/strncmp.S | 236 +++++++++++++++++-----------
> 4 files changed, 269 insertions(+), 214 deletions(-)
>
> --
> 2.17.1
>
_______________________________________________
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-02-16 16:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 17:07 [PATCH v1 0/3] Import Arm Optimized Routines str{n}cmp functions Joey Gouly
2022-02-15 17:07 ` [PATCH v1 1/3] arm64: lib: Import latest version of Arm Optimized Routines' strcmp Joey Gouly
2022-02-16 16:44 ` Russell King (Oracle)
2022-02-16 18:36 ` Robin Murphy
2022-02-17 10:23 ` Joey Gouly
2022-02-25 14:21 ` Will Deacon
2022-02-15 17:07 ` [PATCH v1 2/3] arm64: lib: Import latest version of Arm Optimized Routines' strncmp Joey Gouly
2022-02-15 17:07 ` [PATCH v1 3/3] Revert "arm64: Mitigate MTE issues with str{n}cmp()" Joey Gouly
2022-02-16 16:30 ` Mark Rutland [this message]
2022-02-16 16:52 ` [PATCH v1 0/3] Import Arm Optimized Routines str{n}cmp functions Russell King (Oracle)
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=Yg0mouX04hSRt/r4@lakrids \
--to=mark.rutland@arm.com \
--cc=catalin.marinas@arm.com \
--cc=joey.gouly@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--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 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).