From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: Will Deacon <will@kernel.org>,
Adhemerval Zanella <adhemerval.zanella@linaro.org>,
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>,
Thomas Gleixner <tglx@linutronix.de>,
Eric Biggers <ebiggers@kernel.org>,
Christophe Leroy <christophe.leroy@csgroup.eu>
Subject: Re: [PATCH v5 0/2] arm64: Implement getrandom() in vDSO
Date: Wed, 4 Sep 2024 15:53:42 +0200 [thread overview]
Message-ID: <ZthmZrDUcau5Ebc6@zx2c4.com> (raw)
In-Reply-To: <CAMj1kXHsfmaydb+RCxA1rJPs9K8o4y8LSMTO8sMH-pmAwrZ6PA@mail.gmail.com>
On Wed, Sep 04, 2024 at 02:28:32PM +0200, Ard Biesheuvel wrote:
> On Wed, 4 Sept 2024 at 14:05, Will Deacon <will@kernel.org> wrote:
> >
> > +Ard as he had helpful comments on the previous version.
> >
>
> Thanks for the cc
>
> > On Tue, Sep 03, 2024 at 12:09:15PM +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 v4:
> > > - Improve BE handling.
> > >
> > > Changes from v3:
> > > - Use alternative_has_cap_likely instead of ALTERNATIVE.
> > > - Header/include and comment fixups.
> > >
> > > Changes from v2:
> > > - Refactor Makefile to use same flags for vgettimeofday and
> > > vgetrandom.
> > > - Removed rodata usage and fixed BE on vgetrandom-chacha.S.
> > >
> > > Changes from v1:
> > > - Fixed style issues and typos.
> > > - Added fallback for systems without NEON support.
> > > - Avoid use of non-volatile vector registers in neon chacha20.
> > > - Use c-getrandom-y for vgetrandom.c.
> > > - Fixed TIMENS vdso_rnd_data access.
> > >
> > > Adhemerval Zanella (1):
> > > arm64: vdso: wire up getrandom() vDSO implementation
> > >
> > > Mark Rutland (1):
> > > arm64: alternative: make alternative_has_cap_likely() VDSO compatible
> > >
>
> This looks ok to me now
>
> Reviewed-by: Ard Biesheuvel <ardb@kernel.org>
Great. Thanks a bunch for your reviews, Ard.
Will, if you want to Ack this, I'll queue it up with the other getrandom
vDSO patches for 6.12.
Jason
next prev parent reply other threads:[~2024-09-04 13:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-03 12:09 [PATCH v5 0/2] arm64: Implement getrandom() in vDSO Adhemerval Zanella
2024-09-03 12:09 ` [PATCH v5 1/2] arm64: alternative: make alternative_has_cap_likely() VDSO compatible Adhemerval Zanella
2024-09-03 12:09 ` [PATCH v5 2/2] arm64: vdso: wire up getrandom() vDSO implementation Adhemerval Zanella
2024-09-04 12:05 ` [PATCH v5 0/2] arm64: Implement getrandom() in vDSO Will Deacon
2024-09-04 12:28 ` Ard Biesheuvel
2024-09-04 13:53 ` Jason A. Donenfeld [this message]
2024-09-04 15:02 ` Will Deacon
2024-09-04 15:56 ` Jason A. Donenfeld
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=ZthmZrDUcau5Ebc6@zx2c4.com \
--to=jason@zx2c4.com \
--cc=adhemerval.zanella@linaro.org \
--cc=ardb@kernel.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=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