From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: Theodore Ts'o <tytso@mit.edu>,
linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-arch@vger.kernel.org,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Eric Biggers <ebiggers@kernel.org>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
mark.rutland@arm.com
Subject: Re: [PATCH v4 0/2] arm64: Implement getrandom() in vDSO
Date: Mon, 2 Sep 2024 18:22:24 +0200 [thread overview]
Message-ID: <ZtXmQJx7wCA4fasq@zx2c4.com> (raw)
In-Reply-To: <20240902161912.2751-1-adhemerval.zanella@linaro.org>
On Mon, Sep 02, 2024 at 04:15:45PM +0000, Adhemerval Zanella wrote:
> Implement stack-less ChaCha20 and wire it with the generic vDSO
> getrandom code. The first patch is Mark's fix to the alternatives
> system in the vDSO, while the the second is the actual vDSO work.
>
> Changes from v3:
> - Use alternative_has_cap_likely instead of ALTERNATIVE.
It also has the discussed header/include and comment fixups.
But anyway, this series of two looks fine to me, and I'll gladly queue
it up, pending Will/Catalin's ack on it.
Thanks for working on this.
Jason
prev parent reply other threads:[~2024-09-02 16:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-02 16:15 Adhemerval Zanella
2024-09-02 16:15 ` [PATCH v4 1/2] arm64: alternative: make alternative_has_cap_likely() VDSO compatible Adhemerval Zanella
2024-09-02 16:15 ` [PATCH v4 2/2] arm64: vdso: wire up getrandom() vDSO implementation Adhemerval Zanella
2024-09-02 20:57 ` Ard Biesheuvel
2024-09-03 12:40 ` Adhemerval Zanella Netto
2024-09-02 16:22 ` Jason A. Donenfeld [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=ZtXmQJx7wCA4fasq@zx2c4.com \
--to=jason@zx2c4.com \
--cc=adhemerval.zanella@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=christophe.leroy@csgroup.eu \
--cc=ebiggers@kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=tglx@linutronix.de \
--cc=tytso@mit.edu \
--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®