All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: rep.dot.nop@gmail.com, f4bug@amsat.org, aurelien@aurel32.net,
	qemu-devel@nongnu.org
Subject: Re: [PATCH qemu] mips/malta: pass RNG seed to to kernel via env var
Date: Sat, 1 Oct 2022 21:32:04 +0200	[thread overview]
Message-ID: <20221001213204.3362db80@nbbrfq> (raw)
In-Reply-To: <YziPyCqwl5KIE2cf@zx2c4.com>

On Sat, 1 Oct 2022 21:06:48 +0200
"Jason A. Donenfeld" <Jason@zx2c4.com> wrote:

> On Fri, Sep 30, 2022 at 04:05:20PM +0200, Jason A. Donenfeld wrote:
> > With the kernel patch linked below, Linux ingests a RNG seed
> > passed from the hypervisor. So, pass this for the Malta platform, and
> > reinitialize it on reboot too, so that it's always fresh.
> > 
> > Link: https://lore.kernel.org/linux-mips/20220930140138.575751-1-Jason@zx2c4.com/  
> 
> The kernel side of this has now landed, so we can move ahead on the QEMU
> side:
> https://git.kernel.org/pub/scm/linux/kernel/git/mips/linux.git/commit/?id=056a68cea01edfa78b3474af1bfa39cc6bcc7bee
> 

s/a RNG/an RNG/

What about rngseed=""?
len=min(4711,0)
hex2bin(..0) will return false so ok.
rndseed="0" is problably fine, but is it worthy and desired? 00, 0x0.
Other than that, sounds plausible. IMHO.
thanks,


  reply	other threads:[~2022-10-01 19:42 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-30 14:05 [PATCH qemu] mips/malta: pass RNG seed to to kernel via env var Jason A. Donenfeld
2022-09-30 15:05 ` Daniel P. Berrangé
2022-09-30 15:06   ` Jason A. Donenfeld
2022-10-01 19:06 ` Jason A. Donenfeld
2022-10-01 19:32   ` Bernhard Reutner-Fischer [this message]
2022-10-01 21:33     ` Jason A. Donenfeld
2022-10-03 10:36   ` [PATCH v2] " Jason A. Donenfeld
2022-10-03 18:23     ` Jason A. Donenfeld
2022-10-03 22:36     ` Philippe Mathieu-Daudé
2022-10-03 22:36       ` Philippe Mathieu-Daudé via
2022-10-03 23:07       ` Jason A. Donenfeld
2022-10-04 10:37         ` Jason A. Donenfeld
2022-10-04 10:53           ` Peter Maydell
2022-10-04 10:56             ` Jason A. Donenfeld
2022-10-04 11:00               ` Jason A. Donenfeld
2022-10-04 11:03               ` Peter Maydell
2022-10-04 11:10                 ` Jason A. Donenfeld
2022-10-04 11:39                   ` BALATON Zoltan
2022-10-04 12:08                     ` Jason A. Donenfeld
2022-10-04  8:05       ` Daniel P. Berrangé

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=20221001213204.3362db80@nbbrfq \
    --to=rep.dot.nop@gmail.com \
    --cc=Jason@zx2c4.com \
    --cc=aurelien@aurel32.net \
    --cc=f4bug@amsat.org \
    --cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.