mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alexander Clouter <alex@digriz.org.uk>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [PATCHv2] hw_random: add timeriomem-rng driver
Date: Tue, 10 Feb 2009 19:39:04 +0000	[thread overview]
Message-ID: <20090210193904.GT11872@woodchuck> (raw)
In-Reply-To: <20090210045748.GA17236@gondor.apana.org.au>

Hi,

* Herbert Xu <herbert@gondor.apana.org.au> [2009-02-10 15:57:49+1100]:
> 
> On Sat, Feb 07, 2009 at 09:53:17AM +0000, Alexander Clouter wrote:
> >
> > +/*
> > + * have data return 1, however return 0 if we have nothing
> > + */
> > +static int timeriomem_rng_data_present(struct hwrng *rng, int wait)
> > +{
> > +	s32 delay;
> > +
> > +	if (rng->priv == 0)
> > +		return 1;
> > +
> > +	if (del_timer_sync(&timeriomem_rng_timer)) {
> > +		if (!wait)
> > +			return 0;
> > +
> > +		delay = timeriomem_rng_timer.expires - jiffies;
> > +
> > +		schedule_timeout_uninterruptible(delay);
> > +	}
> 
> Sorry, but this just doesn't work for O_NONBLOCK reads.  What'll
> happen is that the first failed read will return -EAGAIN, and when
> we're called again immediately (because hwrng polling support is
> non-existant), it'll just read the data right away because now
> there is no timer.
>
My original code[1] approach, with timer_pending() in there, would have 
been okay then, right?
----
if (timer_pending(&timeriomem_rng_timer)) {
  if (!wait)
    return 0;

  del_timer_sync(&timeriomem_rng_timer);
  delay = timeriomem_rng_timer.expires - jiffies;

  schedule_timeout_uninterruptible(delay);
}
----
 
> > +static int timeriomem_rng_data_read(struct hwrng *rng, u32 *data)
> > +{
> > +	unsigned long cur;
> > +	s32 delay;
> > +
> > +	*data = readl(timeriomem_rng_data->address);
> > +
> > +	if (rng->priv != 0) {
> > +		cur = jiffies;
> > +
> > +		delay = cur - timeriomem_rng_timer.expires;
> > +		delay = rng->priv - (delay % rng->priv);
> > +
> > +		timeriomem_rng_timer.expires = cur + delay;
> > +		add_timer(&timeriomem_rng_timer);
> > +	}
> 
> Instead of deleting the timer above, why not create a rng->present
> variable which you set to zero here, and the timer sets it to
> non-zero.  Then you just need to return rng->present in your
> data_present function.
> 
Sounds fair, better than the timer_pending approach and easier to 
understand.

> > +static void timeriomem_rng_trigger(unsigned long dummy)
> > +{
> > +	del_timer_sync(&timeriomem_rng_timer);
> > +}
> 
> This is going to create an infinite loop.  There is no point in
> deleting yourself.
> 
Noted.

Cheers

  reply	other threads:[~2009-02-10 19:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-07  9:53 Alexander Clouter
2009-02-10  4:57 ` Herbert Xu
2009-02-10 19:39   ` Alexander Clouter [this message]
2009-02-10 19:49     ` Alexander Clouter
2009-02-11 13:27     ` Herbert Xu

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=20090210193904.GT11872@woodchuck \
    --to=alex@digriz.org.uk \
    --cc=akpm@linux-foundation.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®