From: Will Deacon <will@kernel.org>
To: George Spelvin <lkml@sdf.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2] arm64: ptr auth: Use get_random_u64 instead of _bytes
Date: Tue, 28 Apr 2020 13:58:12 +0100 [thread overview]
Message-ID: <20200428125812.GD6791@willie-the-truck> (raw)
In-Reply-To: <202003311544.02VFiClP011630@sdf.org>
Hi George,
On Tue, Mar 31, 2020 at 03:44:12PM +0000, George Spelvin wrote:
> get_random_bytes() is approximately 4x the cost of two
> get_random_u64() calls, because the former implements
> anti-backtracking.
>
> Because these are authentication keys, useless to an attacker
> as soon as the kernel stops using them, there is no security
> benefit from anti-backtracking.
>
> Signed-off-by: George Spelvin <lkml@sdf.org>
> Cc: Mark Rutland <mark.rutland@arm.com>
> Cc: Will Deacon <will@kernel.org>
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> Cc: linux-arm-kernel@lists.infradead.org
> ---
> v2: Took out all the clever bitmap-based stuff and made a simple
> boring helper function to replace get_random_bytes(&key, 16).
>
> arch/arm64/include/asm/pointer_auth.h | 16 +++++++++++-----
> arch/arm64/kernel/pointer_auth.c | 10 +++++-----
> 2 files changed, 16 insertions(+), 10 deletions(-)
Please can you resend this against the arm64 for-next/ptr-auth branch [1]?
I can't apply it as-is.
Thanks,
Will
[1] https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git/log/?h=for-next/ptr-auth
_______________________________________________
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:[~2020-04-28 12:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-31 15:44 [PATCH v2] arm64: ptr auth: Use get_random_u64 instead of _bytes George Spelvin
2020-03-31 16:22 ` Mark Rutland
2020-04-28 12:58 ` Will Deacon [this message]
2020-05-04 21:07 ` 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=20200428125812.GD6791@willie-the-truck \
--to=will@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=lkml@sdf.org \
--cc=mark.rutland@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