From: William Lee Irwin III <wli@holomorphy.com>
To: Marcelo Tosatti <marcelo@hera.kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: linux-2.4.27 released
Date: Thu, 12 Aug 2004 11:18:51 -0700 [thread overview]
Message-ID: <20040812181851.GP11200@holomorphy.com> (raw)
In-Reply-To: <20040812181712.GO11200@holomorphy.com>
On Thu, Aug 12, 2004 at 11:17:12AM -0700, William Lee Irwin III wrote:
> This patch by nature corrects two apparent bugs which are really one
> bug. p->mm can become NULL while traversing the tasklist. The two
> effects are first that kernel threads appear to be killed. The second
> is that the OOM killing process fails to actually shoot down all threads
> of the chosen process, and so fails to reclaim the memory it intended to.
> oom_kill_task() consists primarily of the expansion of the 2.6 inline
> function get_task_mm().
Incremental atop the mm reference patch:
out_of_memory() attempts to determine whether one jiffies-valued
variable refers to a point in time preceding another jiffies-valued
variable, but does not do so in a jiffies wrap -safe fashion. The
following patch corrects this by using the expansion of the 2.6
macro time_after() to check this condition.
Index: linux-2.4/mm/oom_kill.c
===================================================================
--- linux-2.4.orig/mm/oom_kill.c 2004-06-23 19:41:08.000000000 -0700
+++ linux-2.4/mm/oom_kill.c 2004-06-23 19:50:59.000000000 -0700
@@ -289,7 +289,7 @@
spin_lock(&oom_lock);
reset:
- if (first < now)
+ if ((long)first - (long)now < 0)
first = now;
count = 0;
prev parent reply other threads:[~2004-08-12 18:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-07 23:28 linux-2.4.27 released Marcelo Tosatti
2004-08-10 12:23 ` eth*: transmit timed out since .27 (was: linux-2.4.27 released) Oliver Feiler
2004-08-13 10:15 ` Marcelo Tosatti
2004-08-13 21:56 ` Oliver Feiler
2004-08-12 18:17 ` linux-2.4.27 released William Lee Irwin III
2004-08-12 18:18 ` William Lee Irwin III [this message]
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=20040812181851.GP11200@holomorphy.com \
--to=wli@holomorphy.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@hera.kernel.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