public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Anton Blanchard <anton@samba.org>
To: Anton Altaparmakov <aia21@cantab.net>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: BUG: Current 2.5-BK tree dies on boot!
Date: Thu, 19 Sep 2002 08:58:28 +1000	[thread overview]
Message-ID: <20020918225828.GA2535@krispykreme> (raw)
In-Reply-To: <E17rlgP-0006wL-00@storm.christs.cam.ac.uk>


> This is without preempt. I tried both with and without SMP, with and without
> large TLB pages, with and without pte highmem, all die in the same place.

I needed this to boot the latest BK on my ppc64 box. The question is
why we are suddenly ending up with prev == NULL, hch mentioned his
patch was only a cleanup in this area.

Anton

===== mm/mprotect.c 1.16 vs edited =====
--- 1.16/mm/mprotect.c	Wed Sep 18 04:05:14 2002
+++ edited/mm/mprotect.c	Wed Sep 18 22:44:40 2002
@@ -281,7 +281,7 @@
 		}
 	}
 
-	if (next && prev->vm_end == next->vm_start &&
+	if (prev && next && prev->vm_end == next->vm_start &&
 			can_vma_merge(next, prev->vm_flags) &&
 			!prev->vm_file && !(prev->vm_flags & VM_SHARED)) {
 		spin_lock(&prev->vm_mm->page_table_lock);

  reply	other threads:[~2002-09-18 22:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-18 20:44 BUG: Current 2.5-BK tree dies on boot! Anton Altaparmakov
2002-09-18 22:58 ` Anton Blanchard [this message]
2002-09-19  8:47 ` Jens Axboe
2002-09-19  9:33   ` ide double init? + " Anton Altaparmakov
2002-09-19  9:45     ` Jens Axboe
2002-09-19 10:08       ` Jens Axboe
2002-09-19 10:58         ` Alan Cox
2002-09-19 11:14           ` Jens Axboe
2002-09-19 13:28             ` Alan Cox
2002-09-19 13:27               ` Jens Axboe
2002-09-19 17:48                 ` Patrick Mochel
2002-09-19 18:02                   ` 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=20020918225828.GA2535@krispykreme \
    --to=anton@samba.org \
    --cc=aia21@cantab.net \
    --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