From: Andrew Morton <akpm@linux-foundation.org>
To: Bart Van Assche <bart.vanassche@gmail.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Arjan van de Ven <arjan@infradead.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-kernel <linux-kernel@vger.kernel.org>,
Joe Perches <joe@perches.com>
Subject: Re: [PATCH] timer: Fix jiffies wrap behavior of round_jiffies*()
Date: Wed, 29 May 2013 16:01:50 -0700 [thread overview]
Message-ID: <20130529160150.f0a498d188dc790d018200e9@linux-foundation.org> (raw)
In-Reply-To: <519BC066.5080600@acm.org>
On Tue, 21 May 2013 20:43:50 +0200 Bart Van Assche <bart.vanassche@gmail.com> wrote:
> Make sure that the round_jiffies*() functions return a time that is
> in the future when the jiffies counter is about to wrap.
Actually "when the jiffies counter has recently wrapped".
I assume this was found by inspection?
> @@ -149,9 +149,7 @@ static unsigned long round_jiffies_common(unsigned long j, int cpu,
> /* now that we have rounded, subtract the extra skew again */
> j -= cpu * 3;
> - if (j <= jiffies) /* rounding ate our timeout entirely; */
This used to be a very common bug - we've weeded out many instances but
I'm sure more still remain. We could perhaps have a checkpatch rule
which looks for comparisons against jiffes (and any other
time-measuring variables we can detect) and tells people to use
time_after() and friends, or time_is_*_jiffies().
> - return original;
> - return j;
> + return time_is_after_jiffies(j) ? j : original;
> }
Your email client mangles patches, btw.
next prev parent reply other threads:[~2013-05-29 23:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-21 18:43 Bart Van Assche
2013-05-29 23:01 ` Andrew Morton [this message]
2013-05-29 23:17 ` Joe Perches
2013-05-29 23:38 ` Andrew Morton
2013-05-29 23:48 ` Joe Perches
2013-05-30 0:13 ` Joe Perches
2013-05-30 4:50 ` Andrew Morton
2013-05-30 6:19 ` Bart Van Assche
2013-06-28 15:12 ` [tip:timers/core] timer: Fix jiffies wrap behavior of round_jiffies_common() tip-bot for Bart Van Assche
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=20130529160150.f0a498d188dc790d018200e9@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=bart.vanassche@gmail.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.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
all inboxes | Powered by JetHome®