public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>
Subject: Re: [PATCH] s390: next_timer_interrupt overflow in stop_hz_timer
Date: Mon, 22 May 2006 16:14:28 -0400	[thread overview]
Message-ID: <20060522201428.GA10346@redhat.com> (raw)
In-Reply-To: <200605212100.k4LL0pCX012928@hera.kernel.org>

On Sun, May 21, 2006 at 09:00:51PM +0000, Linux Kernel wrote:
 > commit 92f63cd000059366af18712367216d96180e0ec0
 > tree 4f88c3875afaa8183d6cfcff685e03ac7684d82d
 > parent 0662b71322e211dba9a4bc0e6fbca7861a2b5a7d
 > author Martin Schwidefsky <schwidefsky@de.ibm.com> Sun, 21 May 2006 05:00:25 -0700
 > committer Linus Torvalds <torvalds@g5.osdl.org> Mon, 22 May 2006 02:59:21 -0700
 > 
 > [PATCH] s390: next_timer_interrupt overflow in stop_hz_timer
 > 
 > The 32 bit unsigned substraction (next - jiffies) in stop_hz_timer can
 > overflow if jiffies gets advanced between next_timer_interrupt and the read
 > under the xtime lock.  The cast to a u64 then results in a large value
 > which causes the cpu to wait too long.  Fix this by casting next and
 > jiffies independently to u64 before subtracting them.
 > 
 > (Spotted by Zachary Amsden <zach@vmware.com>)
 > 
 > Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
 > Signed-off-by: Andrew Morton <akpm@osdl.org>
 > Signed-off-by: Linus Torvalds <torvalds@osdl.org>
 > 
 >  arch/s390/kernel/time.c |    2 +-
 >  1 files changed, 1 insertion(+), 1 deletion(-)
 > 
 > diff --git a/arch/s390/kernel/time.c b/arch/s390/kernel/time.c
 > index 029f099..ce19ad4 100644
 > --- a/arch/s390/kernel/time.c
 > +++ b/arch/s390/kernel/time.c
 > @@ -272,7 +272,7 @@ static inline void stop_hz_timer(void)
 >  	next = next_timer_interrupt();
 >  	do {
 >  		seq = read_seqbegin_irqsave(&xtime_lock, flags);
 > -		timer = (__u64)(next - jiffies) + jiffies_64;
 > +		timer = (__u64 next) - (__u64 jiffies) + jiffies_64;
 >  	} while (read_seqretry_irqrestore(&xtime_lock, seq, flags));
 >  	todval = -1ULL;
 >  	/* Be careful about overflows. */


arch/s390/kernel/time.c: In function 'stop_hz_timer':
arch/s390/kernel/time.c:275: error: expected ')' before 'next'
arch/s390/kernel/time.c:275: error: expected ')' before 'jiffies'

		Dave

-- 
http://www.codemonkey.org.uk

       reply	other threads:[~2006-05-22 20:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200605212100.k4LL0pCX012928@hera.kernel.org>
2006-05-22 20:14 ` Dave Jones [this message]
2006-05-23  7:22   ` [PATCH] s390: next_timer_interrupt overflow in stop_hz_timer Martin Schwidefsky

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=20060522201428.GA10346@redhat.com \
    --to=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=schwidefsky@de.ibm.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