public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Con Kolivas <kernel@kolivas.org>
Cc: Andi Kleen <ak@suse.de>, linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: [PATCH] Fix for vmalloc problem was Re: 2.6.10-rc1-mm3
Date: Fri, 5 Nov 2004 14:12:32 +0100	[thread overview]
Message-ID: <20041105131232.GA1030@wotan.suse.de> (raw)
In-Reply-To: <418B6F18.9090404@kolivas.org>

On Fri, Nov 05, 2004 at 11:16:24PM +1100, Con Kolivas wrote:
> Andi Kleen wrote:
> >Con Kolivas <kernel@kolivas.org> writes:
> >
> >
> >>It's life Jim but not as we know it...
> >>
> >>
> >>This happened during modprobe of alsa modules. Keyboard still alive,
> >>everything else dead; not even sysrq would do anything, netconsole had
> >>no output, luckily this made it to syslog:
> >
> >
> >I just tested modprobing of alsa (snd_intel8x0) and it works for me.
> >Also vmalloc must work at least to some point.
> >
> >Can you confirm it's really caused by 4level by reverting all the 
> >4level-* patches from broken out? 
> 
> I dont recall blaming 4level. When I get a chance I'll try.

This patch should fix it. Can you please test? Thanks.

-Andi

Fix silly typo in mm/vmalloc.c and some minor cleanups.

Signed-off-by: Andi Kleen <ak@suse.de>


diff -up linux-2.6.10rc1-mm3/mm/vmalloc.c-o linux-2.6.10rc1-mm3/mm/vmalloc.c
--- linux-2.6.10rc1-mm3/mm/vmalloc.c-o	2004-11-05 11:42:00.000000000 +0100
+++ linux-2.6.10rc1-mm3/mm/vmalloc.c	2004-11-05 14:10:04.000000000 +0100
@@ -98,7 +98,6 @@ static void unmap_area_pgd(pml4_t *pml4,
 	}
 
 	pgd = pml4_pgd_offset_k(pml4, address);
-	address &= ~PML4_MASK;
 	end = address + size;
 
 	do {
@@ -114,8 +113,8 @@ static int map_area_pte(pte_t *pte, unsi
 {
 	unsigned long end;
 
-	address &= ~PMD_MASK;
 	end = address + size;
+	address &= ~PMD_MASK;
 	if (end > PMD_SIZE)
 		end = PMD_SIZE;
 
@@ -187,7 +186,7 @@ void unmap_vm_area(struct vm_struct *are
 	flush_cache_vunmap(address, end);
 	for (i = pml4_index(address); i <= pml4_index(end-1); i++) {
 		next = (address + PML4_SIZE) & PML4_MASK;
-		if (next <= address || next > end)
+		if (next < address || next > end)
 			next = end;
 		unmap_area_pgd(pml4, address, next - address);
 		address = next;
@@ -213,7 +212,7 @@ int map_vm_area(struct vm_struct *area, 
 			err = -ENOMEM;
 			break;
 		}
-		next = (address + PGDIR_SIZE) & PGDIR_MASK;
+		next = (address + PML4_SIZE) & PML4_MASK;
 		if (next < address || next > end)
 			next = end;
 		if (map_area_pgd(pgd, address, next, prot, pages)) {

  parent reply	other threads:[~2004-11-05 13:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20041105001328.3ba97e08.akpm@osdl.org.suse.lists.linux.kernel>
     [not found] ` <418B5C70.7090206@kolivas.org.suse.lists.linux.kernel>
2004-11-05 11:53   ` 2.6.10-rc1-mm3 Andi Kleen
2004-11-05 12:16     ` 2.6.10-rc1-mm3 Con Kolivas
2004-11-05 12:23       ` 2.6.10-rc1-mm3 Andi Kleen
2004-11-05 13:12       ` Andi Kleen [this message]
2004-11-05 13:29         ` [PATCH] Fix for vmalloc problem was 2.6.10-rc1-mm3 Con Kolivas
2004-11-05 13:53           ` Andi Kleen

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=20041105131232.GA1030@wotan.suse.de \
    --to=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=kernel@kolivas.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