From: Tomas Szepe <szepe@pinerecords.com>
To: Colin Gibbs <colin@gibbs.dhs.org>
Cc: linux-kernel@vger.kernel.org, tcallawa@redhat.com,
sparclinux@vger.kernel.org, aurora-sparc-devel@linuxpower.org
Subject: Re: 2.4 SRMMU bug revisited
Date: Mon, 27 May 2002 23:30:16 +0200 [thread overview]
Message-ID: <20020527213016.GB7155@beth.pinerecords.com> (raw)
In-Reply-To: <20020527092408.GD345@louise.pinerecords.com> <1022525198.19147.29.camel@monolith>
> --- 2.4.19-pre4/kernel/fork.c Thu Mar 28 19:49:36 2002
> +++ tortoise-19-pre4/kernel/fork.c Sun Apr 21 22:01:18 2002
> @@ -336,6 +336,9 @@
> if (!mm_init(mm))
> goto fail_nomem;
>
> + if (init_new_context(tsk,mm))
> + goto free_pt;
> +
> down_write(&oldmm->mmap_sem);
> retval = dup_mmap(mm);
> up_write(&oldmm->mmap_sem);
> @@ -347,9 +350,6 @@
> * child gets a private LDT (if there was an LDT in the parent)
> */
> copy_segments(tsk, mm);
> -
> - if (init_new_context(tsk,mm))
> - goto free_pt;
>
> good_mm:
> tsk->mm = mm;
Hmmm, upon closer inspection I found out this patch had *not* been in
what I extracted from the linux-2.4 bitkeeper tree, so my report was
probably not of much value. I'll retest tomorrow with the above applied.
Sorry for the confusion <-- I still can't see the patch in the listings
at http://linux.bkbits.net:8080/linux-2.4/
The patch I used is
http://www.dragon.cz/~kala/patch-2.4.19-pre8-sparcfixes-upto020523-1.gz
(I assembled it by hand using the bk web interface, looking up all sparc
related changes since -pre8.)
T.
next prev parent reply other threads:[~2002-05-28 1:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-27 9:24 2.4 SRMMU bug revisited Tomas Szepe
2002-05-27 10:17 ` David S. Miller
2002-05-27 6:20 ` Tomas Szepe
2002-05-27 10:40 ` David S. Miller
2002-05-27 11:19 ` [aurora-sparc-devel] " Tomas Szepe
2002-05-28 16:41 ` Denis Vlasenko
2002-05-28 12:11 ` David S. Miller
2002-05-27 18:46 ` Colin Gibbs
2002-05-27 19:34 ` Colin Gibbs
2002-05-28 1:12 ` Tomas Szepe
2002-05-27 21:30 ` Tomas Szepe [this message]
2002-05-28 3:41 ` David S. Miller
2002-05-28 5:40 ` Tomas Szepe
2002-05-28 8:39 ` David Woodhouse
2002-05-28 11:58 ` Alan Cox
2002-05-28 11:05 ` David S. Miller
2002-05-28 12:10 ` Ben Collins
2002-05-28 12:19 ` David S. Miller
2002-05-28 0:40 ` David S. Miller
2002-05-29 21:42 ` Tomas Szepe
[not found] <mailman.1022584088.5530.linux-kernel2news@redhat.com>
2002-05-28 16:12 ` Pete Zaitcev
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=20020527213016.GB7155@beth.pinerecords.com \
--to=szepe@pinerecords.com \
--cc=aurora-sparc-devel@linuxpower.org \
--cc=colin@gibbs.dhs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sparclinux@vger.kernel.org \
--cc=tcallawa@redhat.com \
/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