virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Amit Shah <amit.shah@redhat.com>
To: Jason Cooper <jason@lakedaemon.net>
Cc: herbert@gondor.apana.org.au, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org,
	Virtualization List <virtualization@lists.linux-foundation.org>,
	keescook@chromium.org
Subject: Re: [PATCH v2 1/2] hwrng: fetch randomness only after device init
Date: Wed, 9 Jul 2014 18:38:22 +0530	[thread overview]
Message-ID: <20140709130822.GA4553@grmbl.mre> (raw)
In-Reply-To: <20140709115317.GM13433@titan.lakedaemon.net>

On (Wed) 09 Jul 2014 [07:53:17], Jason Cooper wrote:
> On Sat, Jul 05, 2014 at 11:04:52AM +0530, Amit Shah wrote:
> > Commit d9e7972619334 "hwrng: add randomness to system from rng sources"
> > added a call to rng_get_data() from the hwrng_register() function.
> > However, some rng devices need initialization before data can be read
> > from them.
> > 
> > This commit makes the call to rng_get_data() depend on no init fn
> > pointer being registered by the device.  If an init function is
> > registered, this call is made after device init.
> > 
> > CC: Kees Cook <keescook@chromium.org>
> > CC: Jason Cooper <jason@lakedaemon.net>
> > CC: Herbert Xu <herbert@gondor.apana.org.au>
> > CC: <stable@vger.kernel.org> # For v3.15+
> > Signed-off-by: Amit Shah <amit.shah@redhat.com>
> > ---
> >  drivers/char/hw_random/core.c | 31 +++++++++++++++++++++++++------
> >  1 file changed, 25 insertions(+), 6 deletions(-)
> 
> Thanks for cleaning this up!

Thanks!

Any thoughts on the follow-up patch posted later that resolves some of
the weirdness in init?

		Amit

  reply	other threads:[~2014-07-09 13:08 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-05  5:34 [PATCH v2 0/2] hwrng, virtio-rng: init-time fixes Amit Shah
2014-07-05  5:34 ` [PATCH v2 1/2] hwrng: fetch randomness only after device init Amit Shah
2014-07-07  4:41   ` Kees Cook
     [not found]   ` <CAGXu5j+j1LUv_rRpf=03nRfu=Sek5O8TUs8R066JvfbUgT9ZQQ@mail.gmail.com>
2014-07-07  5:53     ` Amit Shah
2014-07-07  6:04       ` Amit Shah
2014-07-07  6:39         ` Amit Shah
2014-07-09 11:53   ` Jason Cooper
2014-07-09 13:08     ` Amit Shah [this message]
2014-07-09 13:17       ` Jason Cooper
2014-07-09 13:25         ` Amit Shah
2014-07-09 16:07           ` [RFC PATCH] hwrng: sysfs entry rng_seed_kernel, was: "Re: [PATCH v2 1/2] hwrng: fetch randomness only after device init" Jason Cooper
2014-07-11 13:26             ` Amit Shah
2014-07-11 15:44               ` Jason Cooper
2014-07-14 21:50                 ` Kees Cook
2014-07-05  5:34 ` [PATCH v2 2/2] virtio: rng: ensure reads happen after successful probe Amit Shah
2014-07-07  4:38   ` Kees Cook
2014-07-07  5:51     ` Amit Shah
2014-07-07  6:09       ` Kees Cook
2014-07-07  6:34         ` Amit Shah
2014-07-09 12:08           ` Jason Cooper
2014-07-09 13:15             ` Amit Shah
2014-07-09 16:18   ` Jason Cooper
2014-07-10  8:45     ` Herbert Xu
2014-07-10  8:52     ` Amit Shah
     [not found]     ` <20140710084514.GA15418@gondor.apana.org.au>
2014-07-10  9:53       ` Amit Shah

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=20140709130822.GA4553@grmbl.mre \
    --to=amit.shah@redhat.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=jason@lakedaemon.net \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=virtualization@lists.linux-foundation.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).