From: Jason Cooper <jason@lakedaemon.net>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Stephan Mueller <smueller@chronox.de>,
Herbert Xu <herbert@gondor.apana.org.au>,
"Pan, Miaoqing" <miaoqing@qti.qualcomm.com>,
Matt Mackall <mpm@selenic.com>,
"miaoqing@codeaurora.org" <miaoqing@codeaurora.org>,
"Valo, Kalle" <kvalo@qca.qualcomm.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
ath9k-devel <ath9k-devel@qca.qualcomm.com>,
"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
"Sepehrdad, Pouyan" <pouyans@qti.qualcomm.com>
Subject: Re: [PATCH 2/2] ath9k: disable RNG by default
Date: Tue, 9 Aug 2016 17:51:08 +0000 [thread overview]
Message-ID: <20160809175108.GE2013@io.lakedaemon.net> (raw)
In-Reply-To: <20160809102458.GA20214@khazad-dum.debian.net>
Hi Henrique,
On Tue, Aug 09, 2016 at 07:24:58AM -0300, Henrique de Moraes Holschuh wrote:
> On Tue, 09 Aug 2016, Stephan Mueller wrote:
> > RHEL 7 and Fedora do not adjust it. So, shall we consider those rng-tools then
> > broken (at least in those large distros)?
>
> Might I humbly suggest that the kernel start providing some metatada
> about the quality of the random source that userspace can consume?
> Preferably by a new ioctl, so that it will fit naturally if we ever
> extend /dev/hwrng to support more than one source?
>
> That would allow for auto tunning to be implemented in userspace...
See my reply to Keith Packard's proposed multi-device hw_random patch:
https://lkml.kernel.org/r/20160809165710.GC2013@io.lakedaemon.net
and top of thread:
https://lkml.kernel.org/r/1469477255-26824-1-git-send-email-keithp@keithp.com
thx,
Jason.
next prev parent reply other threads:[~2016-08-09 17:53 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-09 7:02 [PATCH 1/2] ath9k: change entropy formula for easier understanding miaoqing
2016-08-09 7:02 ` [PATCH 2/2] ath9k: disable RNG by default miaoqing
2016-08-09 7:14 ` Stephan Mueller
2016-08-09 7:35 ` Pan, Miaoqing
2016-08-09 8:07 ` Stephan Mueller
2016-08-09 8:58 ` Herbert Xu
2016-08-09 9:02 ` Stephan Mueller
2016-08-09 9:17 ` Herbert Xu
2016-08-09 9:37 ` Stephan Mueller
2016-08-09 9:46 ` Herbert Xu
2016-08-09 9:56 ` Stephan Mueller
2016-08-09 9:56 ` Herbert Xu
2016-08-09 10:06 ` Stephan Mueller
2016-08-09 10:24 ` Henrique de Moraes Holschuh
2016-08-09 17:51 ` Jason Cooper [this message]
2016-08-10 2:35 ` Pan, Miaoqing
2016-08-10 5:29 ` Stephan Mueller
2016-08-10 6:04 ` Pan, Miaoqing
2016-08-10 6:25 ` Stephan Mueller
2016-08-10 6:46 ` Pan, Miaoqing
2016-08-10 6:51 ` Stephan Mueller
2016-08-10 7:15 ` Pan, Miaoqing
2016-08-10 7:27 ` Stephan Mueller
2016-08-10 7:40 ` Pan, Miaoqing
2016-08-10 7:43 ` Pan, Miaoqing
2016-08-10 13:24 ` Jason Cooper
2016-08-11 2:54 ` miaoqing
2016-08-11 13:14 ` Jason Cooper
2016-08-09 17:48 ` Jason Cooper
2016-09-28 10:00 ` [2/2] " Kalle Valo
2016-09-27 14:53 ` [1/2] ath9k: change entropy formula for easier understanding Kalle Valo
2016-10-13 14:23 ` Kalle Valo
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=20160809175108.GE2013@io.lakedaemon.net \
--to=jason@lakedaemon.net \
--cc=ath9k-devel@qca.qualcomm.com \
--cc=herbert@gondor.apana.org.au \
--cc=hmh@hmh.eng.br \
--cc=kvalo@qca.qualcomm.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=miaoqing@codeaurora.org \
--cc=miaoqing@qti.qualcomm.com \
--cc=mpm@selenic.com \
--cc=pouyans@qti.qualcomm.com \
--cc=smueller@chronox.de \
/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).