summaryrefslogtreecommitdiffstats
path: root/arch/arm64/crypto
diff options
context:
space:
mode:
authorAmit Shah <amit.shah@redhat.com>2014-07-10 15:42:35 +0530
committerHerbert Xu <herbert@gondor.apana.org.au>2014-07-14 20:48:17 +0800
commite052dbf554610e2104c5a7518c4d8374bed701bb (patch)
treeb765a30d4833a04b7576eae0364bcd2d725ac8d0 /arch/arm64/crypto
parentd3cc7996473a7bdd33256029988ea690754e4e2a (diff)
downloadop-kernel-dev-e052dbf554610e2104c5a7518c4d8374bed701bb.zip
op-kernel-dev-e052dbf554610e2104c5a7518c4d8374bed701bb.tar.gz
hwrng: virtio - ensure reads happen after successful probe
The hwrng core asks for random data in the hwrng_register() call itself from commit d9e7972619. This doesn't play well with virtio -- the DRIVER_OK bit is only set by virtio core on a successful probe, and we're not yet out of our probe routine when this call is made. This causes the host to not acknowledge any requests we put in the virtqueue, and the insmod or kernel boot process just waits for data to arrive from the host, which never happens. 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+ Reviewed-by: Jason Cooper <jason@lakedaemon.net> Signed-off-by: Amit Shah <amit.shah@redhat.com> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Diffstat (limited to 'arch/arm64/crypto')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud