From: Steven Rostedt <rostedt@goodmis.org>
To: Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>
Cc: linux-kernel@vger.kernel.org, keir@xensource.com,
Tony Lindgren <tony@atomide.com>,
zach@vmware.com, Ingo Molnar <mingo@elte.hu>,
Thomas Gleixner <tglx@linutronix.de>,
Andreas Mohr <andi@rhlx01.fht-esslingen.de>
Subject: [PATCH] fix bad macro param in timer.c (was: kernel/timer.c: next_timer_interrupt() strange/buggy(?) code (2.6.18-rc1-mm2))
Date: Mon, 17 Jul 2006 21:47:48 -0400 [thread overview]
Message-ID: <1153187268.9932.6.camel@localhost.localdomain> (raw)
In-Reply-To: <20060717185330.GA32264@rhlx01.fht-esslingen.de>
On Mon, 2006-07-17 at 20:53 +0200, Andreas Mohr wrote:
> Hi all,
>
> next_timer_interrupt() contains the following gem:
>
> /* Check tv2-tv5. */
> varray[0] = &base->tv2;
> varray[1] = &base->tv3;
> varray[2] = &base->tv4;
> varray[3] = &base->tv5;
> for (i = 0; i < 4; i++) {
> j = INDEX(i);
> do {
> if (list_empty(varray[i]->vec + j)) {
> j = (j + 1) & TVN_MASK;
> continue;
> }
> list_for_each_entry(nte, varray[i]->vec + j, entry)
> if (time_before(nte->expires, expires))
> expires = nte->expires;
> if (j < (INDEX(i)) && i < 3)
Looking at what INDEX is defined to be:
#define INDEX(N) (base->timer_jiffies >> (TVR_BITS + N * TVN_BITS)) & TVN_MASK
> list = varray[i + 1]->vec + (INDEX(i + 1));
And this INDEX(i+1) is now a ... (TVR_BITS + i + 1 * TVN_BITS)) ...
This doesn't quite look like it suppose to be that way. Probably having
some funny results because of it.
Here's the patch to clean up the macro used to find the index of the
timer vector.
This is definitely a bug fix and should go into 2.6.18
-- Steve
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
Index: linux-2.6.18-rc2/kernel/timer.c
===================================================================
--- linux-2.6.18-rc2.orig/kernel/timer.c 2006-07-17 21:34:08.000000000 -0400
+++ linux-2.6.18-rc2/kernel/timer.c 2006-07-17 21:34:22.000000000 -0400
@@ -408,7 +408,7 @@ static int cascade(tvec_base_t *base, tv
* This function cascades all vectors and executes all expired timer
* vectors.
*/
-#define INDEX(N) (base->timer_jiffies >> (TVR_BITS + N * TVN_BITS)) & TVN_MASK
+#define INDEX(N) (base->timer_jiffies >> (TVR_BITS + (N) * TVN_BITS)) & TVN_MASK
static inline void __run_timers(tvec_base_t *base)
{
next prev parent reply other threads:[~2006-07-18 1:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-17 18:53 kernel/timer.c: next_timer_interrupt() strange/buggy(?) code (2.6.18-rc1-mm2) Andreas Mohr
2006-07-17 19:01 ` Michael Buesch
2006-07-17 19:57 ` Valdis.Kletnieks
2006-07-18 1:50 ` Steven Rostedt
2006-07-18 14:29 ` Michael Buesch
2006-07-18 14:50 ` Valdis.Kletnieks
2006-07-18 15:04 ` Michael Buesch
2006-07-17 20:22 ` Andreas Schwab
2006-07-18 1:47 ` Steven Rostedt [this message]
2006-07-18 1:59 ` [PATCH] fix bad macro param in timer.c Steven Rostedt
2006-07-18 15:14 ` kernel/timer.c: next_timer_interrupt() strange/buggy(?) code (2.6.18-rc1-mm2) Prakash Punnoor
2006-07-18 16:02 ` offtopic boot parameter notsc [Was: Re: kernel/timer.c: next_timer_interrupt() strange/buggy(?) code (2.6.18-rc1-mm2)] Sergio Monteiro Basto
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=1153187268.9932.6.camel@localhost.localdomain \
--to=rostedt@goodmis.org \
--cc=akpm@osdl.org \
--cc=andi@rhlx01.fht-esslingen.de \
--cc=keir@xensource.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=tony@atomide.com \
--cc=torvalds@osdl.org \
--cc=zach@vmware.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
all inboxes | Powered by JetHome®