From: "Jorge Ramirez-Ortiz, Foundries" <jorge@foundries.io>
To: Jorge Ramirez-Ortiz <jorge@foundries.io>
Cc: sumit.garg@linaro.org, mpm@selenic.com,
herbert@gondor.apana.org.au, jens.wiklander@linaro.org,
arnd@arndb.de, ricardo@foundries.io, mike@foundries.io,
gregkh@linuxfoundation.org, op-tee@lists.trustedfirmware.org,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCHv2 2/2] hwrng: optee: fix wait use case
Date: Wed, 5 Aug 2020 15:34:20 +0200 [thread overview]
Message-ID: <20200805133420.GA8276@trex> (raw)
In-Reply-To: <20200723084622.31134-2-jorge@foundries.io>
On 23/07/20, Jorge Ramirez-Ortiz wrote:
> The current code waits for data to be available before attempting a
> second read. However the second read would not be executed as the
> while loop exits.
>
> This fix does not wait if all data has been read and reads a second
> time if only partial data was retrieved on the first read.
>
> This fix also does not attempt to read if not data is requested.
>
> Signed-off-by: Jorge Ramirez-Ortiz <jorge@foundries.io>
> ---
> v2: tidy up the while loop to avoid reading when no data is requested
>
> drivers/char/hw_random/optee-rng.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/char/hw_random/optee-rng.c b/drivers/char/hw_random/optee-rng.c
> index 5bc4700c4dae..a99d82949981 100644
> --- a/drivers/char/hw_random/optee-rng.c
> +++ b/drivers/char/hw_random/optee-rng.c
> @@ -122,14 +122,14 @@ static int optee_rng_read(struct hwrng *rng, void *buf, size_t max, bool wait)
> if (max > MAX_ENTROPY_REQ_SZ)
> max = MAX_ENTROPY_REQ_SZ;
>
> - while (read == 0) {
> + while (read < max) {
> rng_size = get_optee_rng_data(pvt_data, data, (max - read));
>
> data += rng_size;
> read += rng_size;
>
> if (wait && pvt_data->data_rate) {
> - if (timeout-- == 0)
> + if ((timeout-- == 0) || (read == max))
> return read;
> msleep((1000 * (max - read)) / pvt_data->data_rate);
> } else {
any comments please?
next prev parent reply other threads:[~2020-08-05 16:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-23 8:46 [PATCHv2 1/2] hwrng: optee: handle unlimited data rates Jorge Ramirez-Ortiz
2020-07-23 8:46 ` [PATCHv2 2/2] hwrng: optee: fix wait use case Jorge Ramirez-Ortiz
2020-07-24 13:22 ` Sumit Garg
2020-07-24 14:23 ` Jorge Ramirez-Ortiz, Foundries
2020-07-28 10:05 ` Jorge Ramirez-Ortiz, Foundries
2020-08-05 13:49 ` Sumit Garg
2020-08-05 20:38 ` Jorge Ramirez-Ortiz, Foundries
2020-08-06 6:11 ` Sumit Garg
2020-08-06 6:30 ` Jorge Ramirez-Ortiz, Foundries
2020-08-06 6:57 ` Sumit Garg
2020-08-06 8:14 ` Jorge Ramirez-Ortiz, Foundries
2020-08-06 9:15 ` Sumit Garg
2020-08-05 13:34 ` Jorge Ramirez-Ortiz, Foundries [this message]
2020-07-24 13:24 ` [PATCHv2 1/2] hwrng: optee: handle unlimited data rates Sumit Garg
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=20200805133420.GA8276@trex \
--to=jorge@foundries.io \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=herbert@gondor.apana.org.au \
--cc=jens.wiklander@linaro.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mike@foundries.io \
--cc=mpm@selenic.com \
--cc=op-tee@lists.trustedfirmware.org \
--cc=ricardo@foundries.io \
--cc=sumit.garg@linaro.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).