From: Thomas Gleixner <tglx@linutronix.de>
To: Douglas Anderson <dianders@chromium.org>
Cc: John Stultz <john.stultz@linaro.org>,
Andreas Mohr <andi@lisas.de>,
briannorris@chromium.org, huangtao@rock-chips.com,
tony.xie@rock-chips.com, linux-rockchip@lists.infradead.org,
linux@roeck-us.net, heiko@sntech.de, broonie@kernel.org,
djkurtz@chromium.org, tskd08@gmail.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/2] timers: Fix usleep_range() in the context of wake_up_process()
Date: Thu, 20 Oct 2016 23:25:38 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1610202306550.4938@nanos> (raw)
In-Reply-To: <1476995664-15668-1-git-send-email-dianders@chromium.org>
On Thu, 20 Oct 2016, Douglas Anderson wrote:
> - An effort was made to look for users relying on the old behavior by
> looking for usleep_range() in the same file as wake_up_process().
> No problems was found by this search, though it is conceivable that
> someone could have put the sleep and wakeup in two different files.
> - An effort was made to ask several upstream maintainers if they were
> aware of people relying on wake_up_process() to wake up
> usleep_range(). No maintainers were aware of that but they were aware
> of many people relying on usleep_range() never returning before the
> minimum.
Thanks for going the extra mile !
> static void __sched do_usleep_range(unsigned long min, unsigned long max)
> {
> + ktime_t now, end;
> ktime_t kmin;
> u64 delta;
> + int ret;
>
> - kmin = ktime_set(0, min * NSEC_PER_USEC);
> + now = ktime_get();
> + end = ktime_add_us(now, min);
So you calculate the absolute expiry time here.
> delta = (u64)(max - min) * NSEC_PER_USEC;
> - schedule_hrtimeout_range(&kmin, delta, HRTIMER_MODE_REL);
> + do {
> + kmin = ktime_sub(end, now);
> + ret = schedule_hrtimeout_range(&kmin, delta, HRTIMER_MODE_REL);
And then you schedule the thing relative. That does not make sense.
> +
> + /*
> + * If schedule_hrtimeout_range() returns 0 then we actually
> + * hit the timeout. If not then we need to re-calculate the
> + * new timeout ourselves.
> + */
> + if (ret == 0)
> + break;
> +
> + now = ktime_get();
And this is broken because schedule_hrtimeout_range() returns with task
state TASK_RUNNING so the next schedule_hrtimeout_range() will return
-EINTR again because nothing sets the task state back to UNINTERRUPTIBLE.
So instead of sleeping you busy loop.
What you really want to do is something like this:
void __sched usleep_range(unsigned long min, unsigned long max)
{
ktime_t expires = ktime_add_us(ktime_get(), min * NSEC_PER_USEC);
ktime_t delta = ktime_set(0, (u64)(max - min) * NSEC_PER_USEC);
for (;;) {
__set_current_state(TASK_UNINTERRUPTIBLE);
/* Do not return before the requested sleep time has elapsed */
if (!schedule_hrtimeout_range(&expires, delta, HRTIMER_MODE_ABS))
break;
}
}
Thanks,
tglx
next prev parent reply other threads:[~2016-10-20 21:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-20 20:34 [PATCH v3 1/2] timers: Fix usleep_range() in the context of wake_up_process() Douglas Anderson
2016-10-20 20:34 ` [PATCH v3 2/2] timers: Fix documentation for schedule_timeout() and similar Douglas Anderson
[not found] ` <1476995664-15668-2-git-send-email-dianders-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2016-10-20 21:06 ` Thomas Gleixner
2016-10-20 21:25 ` Thomas Gleixner [this message]
2016-10-20 23:36 ` [PATCH v3 1/2] timers: Fix usleep_range() in the context of wake_up_process() Doug Anderson
[not found] ` <CAD=FV=U0sURwAmsiLg0q+=e8o7NfJLWEUAu4zeY1so83cDqXhA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-10-21 7:08 ` Thomas Gleixner
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=alpine.DEB.2.20.1610202306550.4938@nanos \
--to=tglx@linutronix.de \
--cc=andi@lisas.de \
--cc=briannorris@chromium.org \
--cc=broonie@kernel.org \
--cc=dianders@chromium.org \
--cc=djkurtz@chromium.org \
--cc=heiko@sntech.de \
--cc=huangtao@rock-chips.com \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux@roeck-us.net \
--cc=tony.xie@rock-chips.com \
--cc=tskd08@gmail.com \
/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