From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Jorge Ramirez-Ortiz, Foundries" <jorge@foundries.io>
To: op-tee@lists.trustedfirmware.org
Subject: Re: [PATCHv2 2/2] hwrng: optee: fix wait use case
Date: Tue, 28 Jul 2020 12:05:55 +0200
Message-ID: <20200728100555.GA2074@trex>
In-Reply-To: <20200724142305.GA24164@trex>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============8358899844470706591=="
List-Id: <op-tee.lists.trustedfirmware.org>

--===============8358899844470706591==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

On 24/07/20, Jorge Ramirez-Ortiz, Foundries wrote:
> On 24/07/20, Sumit Garg wrote:
> > On Thu, 23 Jul 2020 at 14:16, Jorge Ramirez-Ortiz <jorge@foundries.io> =
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.
> >=20
> > I am not sure how this is possible, can you elaborate?
>=20
> currently, if the user sets max 0, get_optee_rng_data will regardless
> issuese a call to the secure world requesting 0 bytes from the RNG
>=20
> with this patch, this request is avoided.
>=20
> >=20
> > >
> > > 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_rando=
m/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 =3D MAX_ENTROPY_REQ_SZ;
> > >
> > > -       while (read =3D=3D 0) {
> > > +       while (read < max) {
> > >                 rng_size =3D get_optee_rng_data(pvt_data, data, (max - =
read));
> > >
> > >                 data +=3D rng_size;
> > >                 read +=3D rng_size;
> > >
> > >                 if (wait && pvt_data->data_rate) {
> > > -                       if (timeout-- =3D=3D 0)
> > > +                       if ((timeout-- =3D=3D 0) || (read =3D=3D max))
> >=20
> > If read =3D=3D max, would there be any sleep?
>=20
> no but I see no reason why there should be a wait since we already have
> all the data that we need; the msleep is only required when we need to
> wait for the RNG to generate entropy for the number of bytes we are
> requesting. if we are requesting 0 bytes, the entropy is already
> available. at leat this is what makes sense to me.
>=20
>

any further comments?

> >=20
> > -Sumit
> >=20
> > >                                 return read;
> > >                         msleep((1000 * (max - read)) / pvt_data->data_r=
ate);
> > >                 } else {
> > > --
> > > 2.17.1
> > >

--===============8358899844470706591==--