From: Jurriaan <thunder7@xs4all.nl>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.4.21-pre3-ac oops
Date: Sun, 19 Jan 2003 19:17:16 +0100 [thread overview]
Message-ID: <20030119181716.GA28031@middle.of.nowhere> (raw)
In-Reply-To: <Pine.LNX.4.44.0301191347310.2280-100000@localhost.localdomain>
From: Hugh Dickins <hugh@veritas.com>
Date: Sun, Jan 19, 2003 at 02:08:40PM +0000
> If you got 2.4.21-pre3-ac __free_pages_ok oops, please try this patch.
>
> Hugh
>
> --- 2.4.21-pre3-ac4/kernel/fork.c Mon Jan 13 18:56:12 2003
> +++ linux/kernel/fork.c Sun Jan 19 13:39:37 2003
> @@ -688,6 +688,8 @@
> p->lock_depth = -1; /* -1 = no lock */
> p->start_time = jiffies;
>
> + INIT_LIST_HEAD(&p->local_pages);
> +
> retval = -ENOMEM;
> /* copy all the process information */
> if (copy_files(clone_flags, p))
>
If this is it, and so far it looks like it for me, wouldn't it be time
to create a
CONFIG_DEBUG_LIST
option that caught these illegal list manipulations?
I know - talk is cheap, code isn't etc etc :-)
Jurriaan
--
pay no deposit and get no return
Skyclad - No Deposit, No Return
GNU/Linux 2.4.21-pre3-ac4 SMP/ReiserFS 2x2785 bogomips load av: 0.06 0.82 0.64
next prev parent reply other threads:[~2003-01-19 18:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-19 14:08 [PATCH] 2.4.21-pre3-ac oops Hugh Dickins
2003-01-19 18:17 ` Jurriaan [this message]
2003-01-19 20:13 ` Tupshin Harper
2003-01-19 21:27 ` Bryan Andersen
2003-01-19 21:28 ` Andre Hedrick
2003-01-19 21:58 ` Tupshin Harper
2003-01-19 22:15 ` Bryan Andersen
2003-01-19 23:27 ` Andre Hedrick
2003-01-20 18:51 ` Bryan Andersen
2003-01-19 22:13 ` Ralf Hildebrandt
2003-01-20 8:37 ` Alan Cox
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=20030119181716.GA28031@middle.of.nowhere \
--to=thunder7@xs4all.nl \
--cc=linux-kernel@vger.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 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.