From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Eric Biggers <ebiggers@kernel.org>
Cc: Christophe Leroy <christophe.leroy@csgroup.eu>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"patches@lists.linux.dev" <patches@lists.linux.dev>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
"linux-api@vger.kernel.org" <linux-api@vger.kernel.org>,
"x86@kernel.org" <x86@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>,
Carlos O'Donell <carlos@redhat.com>,
Florian Weimer <fweimer@redhat.com>,
Arnd Bergmann <arnd@arndb.de>, Jann Horn <jannh@google.com>,
Christian Brauner <brauner@kernel.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH v12 0/6] implement getrandom() in vDSO
Date: Wed, 21 Dec 2022 15:25:49 +0100 [thread overview]
Message-ID: <Y6MXbTAHBSR5WBrU@zx2c4.com> (raw)
In-Reply-To: <Y6IXWltScF2CI1v3@gmail.com>
On Tue, Dec 20, 2022 at 08:13:14PM +0000, Eric Biggers wrote:
> On Tue, Dec 20, 2022 at 05:17:52PM +0000, Christophe Leroy wrote:
> > Hi Jason,
> >
> > Le 12/12/2022 à 19:53, Jason A. Donenfeld a écrit :
> > > Changes v11->v12:
> > > ----------------
> > > - In order to avoid mlock()ing pages, and the related rlimit and fork
> > > inheritance issues there, Introduce VM_DROPPABLE to prevent swapping
> > > while meeting the cache-like requirements of vDSO getrandom().
> > >
> > > This has some tenticles in mm/ and arch/x86/ code, so I've marked the
> > > two patches for that as still RFC, while the rest of the series is not
> > > RFC.
> > >
> > > - Mandate that opaque state blobs don't straddle page boundaries, so
> > > that VM_DROPPABLE can work on page-level granularity rather than
> > > allocation-level granularity.
> > >
> > > - Add compiler barriers to vDSO getrandom() to prevent theoretical
> > > reordering potential.
> > >
> > > - Initialize the trials loop counter in the chacha test.
> >
> > I would have liked to give it a try on powerpc, but the series
> > conflicts. I tried both on v6.1 and on linus/master from now:
> >
>
> Same here, I can't figure out how to apply this series.
Rebased v13 posted: https://lore.kernel.org/all/20221221142327.126451-1-Jason@zx2c4.com/
Jason
next prev parent reply other threads:[~2022-12-21 14:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 18:53 [PATCH v12 0/6] implement getrandom() in vDSO Jason A. Donenfeld
2022-12-12 18:53 ` [PATCH RFC v12 1/6] mm: add VM_DROPPABLE for designating always lazily freeable mappings Jason A. Donenfeld
2022-12-12 18:53 ` [PATCH RFC v12 2/6] x86: mm: Skip faulting instruction for VM_DROPPABLE faults Jason A. Donenfeld
2022-12-12 21:01 ` Jason A. Donenfeld
2022-12-12 18:53 ` [PATCH v12 3/6] random: add vgetrandom_alloc() syscall Jason A. Donenfeld
2022-12-12 18:53 ` [PATCH v12 4/6] arch: allocate vgetrandom_alloc() syscall number Jason A. Donenfeld
2022-12-12 18:53 ` [PATCH v12 5/6] random: introduce generic vDSO getrandom() implementation Jason A. Donenfeld
2022-12-12 18:53 ` [PATCH v12 6/6] x86: vdso: Wire up getrandom() vDSO implementation Jason A. Donenfeld
2022-12-20 17:17 ` [PATCH v12 0/6] implement getrandom() in vDSO Christophe Leroy
2022-12-20 20:13 ` Eric Biggers
2022-12-21 14:25 ` Jason A. Donenfeld [this message]
2022-12-21 20:48 ` Eric Biggers
2022-12-21 14:04 ` 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=Y6MXbTAHBSR5WBrU@zx2c4.com \
--to=jason@zx2c4.com \
--cc=adhemerval.zanella@linaro.org \
--cc=arnd@arndb.de \
--cc=brauner@kernel.org \
--cc=carlos@redhat.com \
--cc=christophe.leroy@csgroup.eu \
--cc=ebiggers@kernel.org \
--cc=fweimer@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=jannh@google.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=patches@lists.linux.dev \
--cc=tglx@linutronix.de \
--cc=x86@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).