All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: David Fries <david@fries.net>
Cc: tglx@linutronix.de, linux-kernel@vger.kernel.org,
	"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH] system timer: fix crash in <100Hz system timer
Date: Mon, 7 Jan 2008 15:36:50 -0800	[thread overview]
Message-ID: <20080107153650.0cb85eeb.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080105221653.GA10065@spacedout.fries.net>

On Sat, 5 Jan 2008 16:16:55 -0600
David Fries <david@fries.net> wrote:

> The kernel has a divide by zero crash when trying to run the system
> timer less than 100Hz.  The problem is x/(HZ/USER_HZ) and related.
> Now x*(USER_HZ/HZ) will be used if HZ<USER_HZ.
> 
> I'm running the Linux kernel under qemu and went to run a slower
> system timer to take less CPU (and battery) on the host.  I found that
> the kernel paniced under emulation because of a divide by zero in
> three places.  Here is the patch.  The base git was updated today
> 01-05-2008.  I went for a 20Hz system time by adding config HZ_20 etc
> to kernel/Kconfig.hz.  With this patch I verified the system timer by
> looking at /proc/interrupts.
> 
> Signed-off-by: David Fries <david@fries.net>
> 
> -- 
> David Fries <david@fries.net>
> http://fries.net/~david/ (PGP encryption key available)
> 
> 
> diff --git a/include/linux/acct.h b/include/linux/acct.h
> index 302eb72..86b848d 100644
> --- a/include/linux/acct.h
> +++ b/include/linux/acct.h
> @@ -173,7 +173,11 @@ typedef struct acct acct_t;
>  static inline u32 jiffies_to_AHZ(unsigned long x)
>  {
>  #if (TICK_NSEC % (NSEC_PER_SEC / AHZ)) == 0
> -	return x / (HZ / AHZ);
> +	#if HZ < AHZ
> +		return x * (AHZ / HZ);
> +	#else
> +		return x / (HZ / AHZ);
> +	#endif
>  #else
>          u64 tmp = (u64)x * TICK_NSEC;
>          do_div(tmp, (NSEC_PER_SEC / AHZ));
> diff --git a/kernel/time.c b/kernel/time.c
> index 09d3c45..23af26f 100644
> --- a/kernel/time.c
> +++ b/kernel/time.c
> @@ -565,7 +565,11 @@ EXPORT_SYMBOL(jiffies_to_timeval);
>  clock_t jiffies_to_clock_t(long x)
>  {
>  #if (TICK_NSEC % (NSEC_PER_SEC / USER_HZ)) == 0
> +	#if HZ < USER_HZ
> +	return x * (USER_HZ / HZ);
> +	#else
>  	return x / (HZ / USER_HZ);
> +	#endif
>  #else
>  	u64 tmp = (u64)x * TICK_NSEC;
>  	do_div(tmp, (NSEC_PER_SEC / USER_HZ));
> @@ -598,7 +602,12 @@ EXPORT_SYMBOL(clock_t_to_jiffies);
>  u64 jiffies_64_to_clock_t(u64 x)
>  {
>  #if (TICK_NSEC % (NSEC_PER_SEC / USER_HZ)) == 0
> -	do_div(x, HZ / USER_HZ);
> +	#if HZ < USER_HZ
> +		x *= USER_HZ;
> +		do_div(x, HZ);
> +	#else
> +		do_div(x, HZ / USER_HZ);
> +	#endif
>  #else
>  	/*
>  	 * There are better ways that don't overflow early,

Alas, I get 100% rejects due to conflicting changes from Peter's
avoid-overflows-in-kernel-timec.patch.

Peter, did that patch propagate this failure, or might it have happily
fixed it?


  reply	other threads:[~2008-01-07 23:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-05 22:16 [PATCH] system timer: fix crash in <100Hz system timer David Fries
2008-01-07 23:36 ` Andrew Morton [this message]
2008-01-07 23:51   ` H. Peter Anvin
2008-01-08  0:09     ` Andrew Morton
2008-01-09  7:15 ` Andrew Morton

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=20080107153650.0cb85eeb.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=david@fries.net \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.