From: Babis Chalios <bchalios@amazon.es>
To: Olivia Mackall <olivia@selenic.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Theodore Ts'o <tytso@mit.edu>,
"Jason A. Donenfeld" <Jason@zx2c4.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Jason Wang" <jasowang@redhat.com>,
Xuan Zhuo <xuanzhuo@linux.alibaba.com>,
<linux-crypto@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<virtualization@lists.linux-foundation.org>
Cc: <graf@amazon.de>, <xmarcalx@amazon.co.uk>, <aams@amazon.de>,
<dwmw@amazon.co.uk>, <gregkh@linuxfoundation.org>,
<bchalios@amazon.es>
Subject: Re: [RFC PATCH 0/2] Propagating reseed notifications to user space
Date: Mon, 4 Sep 2023 15:44:48 +0200 [thread overview]
Message-ID: <32756034-2fd4-4246-830e-c1a0eeab0a55@amazon.es> (raw)
In-Reply-To: <20230823090107.65749-1-bchalios@amazon.es>
Hello all,
On 23/8/23 11:01, Babis Chalios wrote:
> This is an RFC, so that we can discuss whether the proposed ABI works.
> Also, I'd like to hear people's opinion on the internal registration
> API, 8/24 split etc. If we decide that this approach works, I 'm happy
> to add documentation for it, with examples on how user space can make
> use of it.
Some time has passed since I sent this and I haven't received any
comments, so I assume people
are happy with the proposed API. I will work on adding documentation and
examples on how
user space can use this and send a v1.
Cheers,
Babis
next prev parent reply other threads:[~2023-09-04 13:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-23 9:01 [RFC PATCH 0/2] Propagating reseed notifications to user space Babis Chalios
2023-08-23 9:01 ` [RFC PATCH 1/2] random: emit reseed notifications for PRNGs Babis Chalios
2023-08-23 9:08 ` Greg KH
2023-08-23 9:27 ` Babis Chalios
2023-08-23 10:06 ` Greg KH
[not found] ` <89ce1064-e4a3-461f-8a78-88e72e5b6419@amazon.es>
2023-08-23 10:20 ` Alexander Graf
2023-08-23 10:25 ` Greg KH
2023-08-23 10:37 ` Alexander Graf
2023-08-23 9:01 ` [RFC PATCH 2/2] virtio-rng: implement entropy leak feature Babis Chalios
2023-09-04 13:44 ` Babis Chalios [this message]
2023-09-04 14:42 ` [RFC PATCH 0/2] Propagating reseed notifications to user space Jason A. Donenfeld
2023-09-04 14:54 ` Babis Chalios
2023-09-06 14:25 ` Alexander Graf
2023-09-17 13:34 ` Yann Droneaud
2023-09-18 8:32 ` Alexander Graf
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=32756034-2fd4-4246-830e-c1a0eeab0a55@amazon.es \
--to=bchalios@amazon.es \
--cc=Jason@zx2c4.com \
--cc=aams@amazon.de \
--cc=dwmw@amazon.co.uk \
--cc=graf@amazon.de \
--cc=gregkh@linuxfoundation.org \
--cc=herbert@gondor.apana.org.au \
--cc=jasowang@redhat.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=olivia@selenic.com \
--cc=tytso@mit.edu \
--cc=virtualization@lists.linux-foundation.org \
--cc=xmarcalx@amazon.co.uk \
--cc=xuanzhuo@linux.alibaba.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