mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: <bchalios@amazon.es>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>,
	Olivia Mackall <olivia@selenic.com>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	Jason Wang <jasowang@redhat.com>, <linux-crypto@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>,
	<virtualization@lists.linux-foundation.org>, <amit@kernel.org>,
	<graf@amazon.de>, <xmarcalx@amazon.co.uk>
Subject: Re: [PATCH 0/2] [RFC] virtio-rng entropy leak reporting feature
Date: Fri, 20 Jan 2023 15:27:58 +0100	[thread overview]
Message-ID: <2e0e51a5-d852-241d-3c3a-5440296bc896@amazon.es> (raw)
In-Reply-To: <Y8qjLolaLbMnDnkw@zx2c4.com>



On 1/20/23 3:20 PM, "Jason A. Donenfeld" <Jason@zx2c4.com> wrote:
> CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe.
> 
> 
> 
> Hi Babis,
> 
> As I mentioned to you privately this week, I'm about to be out of town,
> so I won't be able to look at this until I'm back in a few weeks. I
> appreciate your patience.
> 
> But as a cursory look, I'm happy that you've written the hardware-side
> code for this. That's a great starting point. The plumbing is not so
> nice, though. This needs to be integrated more closely with random.c
> itself, similar to how vmgenid works.
> 
> When I'm back in a few weeks, I'll see if I can either write a
> description of what I have in mind, or simply integrate the useful
> hardware work here into an expanded patch series.
> 
> [Please don't merge anything for now.]
> 
> Jason
> 

Hey Jason,

I agree that the plumbing with random.c needs work. That's why this is an RFC! That's the kind of input I'm looking for.
As I mention in the cover letter, IMHO, we need to give to random.c (and other parts of the kernel that they might need it)
an API to directly add buffers in the queue, so that we avoid the race-condition here.

Any ideas on that front are more than welcome and looking forward to them.

Cheers,
Babis
Amazon Spain Services sociedad limitada unipersonal, Calle Ramirez de Prado 5, 28045 Madrid. Registro Mercantil de Madrid . Tomo 22458 . Folio 102 . Hoja M-401234 . CIF B84570936

      reply	other threads:[~2023-01-20 14:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-19 18:43 Babis Chalios
2023-01-19 18:43 ` [PATCH 1/2] virtio-rng: implement entropy leak feature Babis Chalios
2023-01-19 20:17   ` kernel test robot
2023-01-20  1:24   ` kernel test robot
2023-01-20 12:32   ` Michael S. Tsirkin
2023-01-20 12:54     ` Babis Chalios
2023-01-20 15:07     ` Elliott, Robert (Servers)
2023-01-19 18:43 ` [PATCH 2/2] virtio-rng: add sysfs entries for leak detection Babis Chalios
2023-01-19 22:31   ` kernel test robot
2023-01-19 22:51   ` kernel test robot
2023-01-20  3:07   ` kernel test robot
2023-01-20 14:20 ` [PATCH 0/2] [RFC] virtio-rng entropy leak reporting feature Jason A. Donenfeld
2023-01-20 14:27   ` bchalios [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=2e0e51a5-d852-241d-3c3a-5440296bc896@amazon.es \
    --to=bchalios@amazon.es \
    --cc=Jason@zx2c4.com \
    --cc=amit@kernel.org \
    --cc=graf@amazon.de \
    --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=virtualization@lists.linux-foundation.org \
    --cc=xmarcalx@amazon.co.uk \
    /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®