From: Bryan Andersen <bryan@bogonomicon.net>
To: Byron Stanoszek <gandalf@winds.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [OOPS] linux-2.4.21-pre3-ac4 @ free_pages_ok()
Date: Fri, 24 Jan 2003 14:22:03 -0600 [thread overview]
Message-ID: <3E31A06B.6020508@bogonomicon.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0301240958340.15579-100000@winds.org>
Actually a patch is already out there.
From: hugh@veritas.com
Subject: [PATCH] 2.4.21-pre3-ac oops
--- 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))
-- Bryan
Byron Stanoszek wrote:
> I've seen this oops report before, but since nobody's posted a fix for it or
> anything, I figured I'll post the one I saw. I got a series of two oopses after
> untarring a 200MB tarfile. (The system has 512MB of memory and was recently
> booted into 2.4.21-pre3-ac4). Here they are, plus boot-dmesg at the bottom.
prev parent reply other threads:[~2003-01-24 20:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-24 15:01 Byron Stanoszek
2003-01-24 20:22 ` Bryan Andersen [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=3E31A06B.6020508@bogonomicon.net \
--to=bryan@bogonomicon.net \
--cc=gandalf@winds.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®