linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
To: 'Wolfgang Wander' <wwc@rentec.com>
Cc: 'Andrew Morton' <akpm@osdl.org>,
	herve@elma.fr, mingo@elte.hu, arjanv@redhat.com,
	linux-mm@kvack.org, colin.harrison@virgin.net
Subject: RE: [PATCH] Avoiding mmap fragmentation - clean rev
Date: Thu, 26 May 2005 10:44:05 -0700	[thread overview]
Message-ID: <200505261744.j4QHi4g22996@unix-os.sc.intel.com> (raw)
In-Reply-To: <4296082A.3000900@rentec.com>

Wolfgang Wander wrote on Thursday, May 26, 2005 10:32 AM
> This one seems to have triggered already the second bug report on lkm.
> 
> Is it possible that  in
> 
> static void
> detach_vmas_to_be_unmapped(struct mm_struct *mm, struct vm_area_struct *vma,
>      struct vm_area_struct *prev, unsigned long end)
> {
>      struct vm_area_struct **insertion_point;
>      struct vm_area_struct *tail_vma = NULL;
> 
>      insertion_point = (prev ? &prev->vm_next : &mm->mmap);
>      do {
>          rb_erase(&vma->vm_rb, &mm->mm_rb);
>          mm->map_count--;
>          tail_vma = vma;
>          vma = vma->vm_next;
>      } while (vma && vma->vm_start < end);
>      *insertion_point = vma;
>      tail_vma->vm_next = NULL;
>      if (mm->unmap_area == arch_unmap_area)
>          tail_vma->vm_private_data = (void*) prev->vm_end;
>      else
>          tail_vma->vm_private_data = vma ?
>              (void*) vma->vm_start : (void*) mm->mmap_base;
>      mm->mmap_cache = NULL;        /* Kill the cache. */
> }
> 
> 'prev' seems to possibly be NULL and the assignemnt of
>    tail_vma->vm_private_data = (void*) prev->vm_end;
> which fix-2 adds does not check for that.
> That potential problem does not seem to match the stacktrace
> below however...

It sure looks like 'prev' can be null.  It needs the similar check
like the one in the top down case.  I will double check on it.  Thanks
for catching the bug.

- Ken

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>

  reply	other threads:[~2005-05-26 17:44 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E4BA51C8E4E9634993418831223F0A49291F06E1@scsmsx401.amr.corp.intel.com>
2005-05-17 22:28 ` Chen, Kenneth W
2005-05-18  7:28   ` Arjan van de Ven
2005-05-18  7:43     ` Ingo Molnar
2005-05-18  7:37   ` Ingo Molnar
2005-05-18 13:05   ` Wolfgang Wander
2005-05-18 15:47   ` Wolfgang Wander
2005-05-18 16:18     ` Chen, Kenneth W
2005-05-18 17:16       ` Wolfgang Wander
2005-05-18 17:57         ` Chen, Kenneth W
2005-05-19 18:38           ` Wolfgang Wander
2005-05-19 22:54             ` Andrew Morton
2005-05-20  2:02               ` Chen, Kenneth W
2005-05-20 23:51               ` Chen, Kenneth W
2005-05-23 18:25                 ` Wolfgang Wander
2005-05-26 17:32                 ` Wolfgang Wander
2005-05-26 17:44                   ` Chen, Kenneth W [this message]
2005-05-20  3:10             ` Chen, Kenneth W
2005-05-20 12:39               ` Wolfgang Wander
2005-05-20  2:14 Chen, Kenneth W
2005-05-20 12:47 ` Wolfgang Wander
2005-05-25  7:30 linux
2005-05-27 16:37 Chen, Kenneth W

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=200505261744.j4QHi4g22996@unix-os.sc.intel.com \
    --to=kenneth.w.chen@intel.com \
    --cc=akpm@osdl.org \
    --cc=arjanv@redhat.com \
    --cc=colin.harrison@virgin.net \
    --cc=herve@elma.fr \
    --cc=linux-mm@kvack.org \
    --cc=mingo@elte.hu \
    --cc=wwc@rentec.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