linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Schlichter <schlicht@uni-mannheim.de>
To: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Cc: Andrew Morton <akpm@osdl.org>
Subject: Re: 2.6.0-test8-mm1
Date: Mon, 20 Oct 2003 13:18:31 +0200	[thread overview]
Message-ID: <200310201318.36486.schlicht@uni-mannheim.de> (raw)
In-Reply-To: <20031020020558.16d2a776.akpm@osdl.org>


[-- Attachment #1.1: Type: text/plain, Size: 421 bytes --]

On Monday 20 October 2003 11:05, Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.0-test8/2
>.6.0-test8-mm1
  ~~ snip ~~
> +fix-sqrt.patch
>
>  Fix int_sqrt().

I really like this one... ;-)

The problem ist that oom_kill.c assumes that int_sqrt() never returns 0. So we 
could get a division by zero there :-(

The attached patch fixes that...

Regards
   Thomas

[-- Attachment #1.2: fix-oom_kill.diff --]
[-- Type: text/x-diff, Size: 538 bytes --]

--- linux-2.6.0-test8-mm1/mm/oom_kill.c.orig	Mon Oct 20 12:49:58 2003
+++ linux-2.6.0-test8-mm1/mm/oom_kill.c	Mon Oct 20 12:52:55 2003
@@ -63,8 +63,8 @@
 	cpu_time = (p->utime + p->stime) >> (SHIFT_HZ + 3);
 	run_time = (get_jiffies_64() - p->start_time) >> (SHIFT_HZ + 10);
 
-	points /= int_sqrt(cpu_time);
-	points /= int_sqrt(int_sqrt(run_time));
+	points /= cpu_time ? int_sqrt(cpu_time) : 1;
+	points /= run_time ? int_sqrt(int_sqrt(run_time)) : 1;
 
 	/*
 	 * Niced processes are most likely less important, so double

[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-10-20 11:18 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-20  9:05 2.6.0-test8-mm1 Andrew Morton
2003-10-20 11:18 ` Thomas Schlichter [this message]
2003-10-20 15:32 ` 2.6.0-test8-mm1 John Cherry
2003-10-20 16:11 ` 2.6.0-test8-mm1 Thomas Schlichter
2003-10-20 21:48   ` 2.6.0-test8-mm1 Andrew Morton
2003-10-20 22:01     ` 2.6.0-test8-mm1 Thomas Schlichter
2003-10-20 22:17       ` 2.6.0-test8-mm1 Andrew Morton
2003-10-20 22:30         ` 2.6.0-test8-mm1 Thomas Schlichter
2003-10-21  0:43           ` 2.6.0-test8-mm1 Thomas Schlichter
2003-10-21  0:14       ` 2.6.0-test8-mm1 Valdis.Kletnieks
2003-10-21  0:27         ` 2.6.0-test8-mm1 Andrew Morton
2003-10-21  0:46           ` 2.6.0-test8-mm1 Valdis.Kletnieks
2003-10-21  1:56             ` 2.6.0-test8-mm1 Andrew Morton
2003-10-21  2:54               ` 2.6.0-test8-mm1 Valdis.Kletnieks
2003-10-21  3:49               ` 2.6.0-test8-mm1 Jeremy Fitzhardinge
2003-10-21  8:39               ` 2.6.0-test8-mm1 Thomas Schlichter
2003-10-21 17:47               ` 2.6.0-test8-mm1 James Simmons
2003-10-21 20:23                 ` 2.6.0-test8-mm1 Helge Hafting
2003-10-21 20:36                   ` 2.6.0-test8-mm1 Thomas Schlichter
2003-10-21 20:42                     ` 2.6.0-test8-mm1 James Simmons
2003-10-21 22:53                       ` 2.6.0-test8-mm1 Thomas Schlichter
2003-10-21 23:27                         ` 2.6.0-test8-mm1 Robert Love
2003-10-22  2:46                           ` 2.6.0-test8-mm1 Valdis.Kletnieks
2003-10-20 19:21 ` [BUG] 2.6.0-test8-mm1 Ramón Rey Vicente
2003-10-20 20:10   ` Andrew Morton
2003-10-20 21:53     ` Ramón Rey Vicente

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=200310201318.36486.schlicht@uni-mannheim.de \
    --to=schlicht@uni-mannheim.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    /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